Open Chrome profile files in your browser
The folder where Chrome keeps what you browse: History, Bookmarks and the tabs it reopens. Open it right here as a card of your visits, searches, tabs, bookmarks and downloads. Nothing leaves your device.
Or drop it anywhere on this page
What you'll see
Your browser’s files open as a card of how you browse: your visits and searches, the tabs open and closed, your bookmarks and downloads, worked out on your device.
- History • Your visits, searches and the sites you went to most each year
- Tabs • Open and closed, each with its back and forward pages
- Bookmarks and Reading List • In their folders
- Passwords, cookies and autofill • Kept shut, never read
About Chrome profile
Chrome keeps each person’s browsing in a profile folder, Default for the first and Profile 1 and on for the others, under Google/Chrome/User Data in AppData on Windows, in Application Support on a Mac and in .config on Linux. Edge, Brave, Opera and Vivaldi are built on Chromium and keep the same files in folders of their own.
History is a SQLite database of every page you went to, each visit with how you got there, the words you searched for and your downloads. Bookmarks is a JSON file and Top Sites the pages the new tab page offers. The Sessions folder holds Session_ files of the windows and tabs that were open, with each tab’s back and forward pages, and Tabs_ files of the tabs you closed. Login Data, Cookies and Web Data keep saved passwords, cookies and autofill.
Filepeek reads History, Bookmarks, Top Sites and the session files into a card: your visits, pages and sites, how many you typed in, your busiest day, the sites you went to most each year, your searches, the tabs open with their back and forward pages, the tabs you closed, your bookmarks by folder and your downloads. Login Data, Cookies and Web Data stay shut: Filepeek never reads them, and the card only names them.
Chrome profile folder
.sqlite • .json
Format
- MIME type
- inode/directory
- Made by
- Google Chrome, and Microsoft Edge, Brave, Opera and Vivaldi, which keep the same files
- Released
- 2008
Inside the file
- Kept as
- A folder a profile, Default for the first
- History
- SQLite, with visits, searches and downloads
- Tabs
- Session_ and Tabs_ files in Sessions
- Kept shut
- Login Data, Cookies and Web Data
Opens in every browser
Filepeek opens Chrome, Edge, Brave, Opera and Vivaldi profiles in Chrome, Edge, Firefox and Safari. Drop the profile’s folder on the page, or its History alone. On their own, browsers can’t open a profile’s files.
- YouChromeOpens through Filepeek
- YouEdgeOpens through Filepeek
- YouFirefoxOpens through Filepeek
- YouSafariOpens through Filepeek
Apps that open Chrome profile
- WindowsChrome reads it as its own profile • No app opens its files
- MacChrome reads it as its own profile • No app opens its files
- iPhone and iPadNo app reads it
- AndroidNo app reads it
Questions
Where is my Chrome profile?
On Windows it’s in %LOCALAPPDATA%\Google\Chrome\User Data\Default, on a Mac in ~/Library/Application Support/Google/Chrome/Default and on Linux in ~/.config/google-chrome/Default. chrome://version shows the Profile Path of the profile you’re in. Quit Chrome first, so its files are whole.
How do I get back tabs Chrome lost?
Drop the profile with its Sessions folder. Its Session_ files keep the windows that were open and its Tabs_ files the tabs you closed, each with the pages behind its back button, so the card lists their addresses to open again.
Does it show my saved passwords?
No. Login Data, Cookies and Web Data hold your saved passwords, cookies, cards and autofill. Filepeek never reads them: the card only names them as kept shut.
Does it open Edge, Brave and Opera profiles?
Yes. They’re built on Chromium and keep the same History, Bookmarks and Sessions: Edge’s under Microsoft\Edge\User Data and Brave’s under BraveSoftware\Brave-Browser\User Data. Filepeek names the browser from the profile’s Preferences.
Why are older visits missing?
Chrome keeps 90 days of history and drops the visits before that, and an incognito window’s visits are never written down. Pages inside a frame and reloads aren’t on chrome://history either.