Free Browser History Viewer: Open Chrome, Firefox and Safari History Files

How to Open Your Browser History File

1. Quit the browser completely

   Close every window of the browser whose history you want. On Windows, check the system tray too, because Chrome and Edge can keep running in the background. This lets the browser finish writing and unlock the file.

2. Find the history file

   Use the table further down this page, or open chrome://version (edge://version, brave://version) and copy the “Profile path”. In Firefox, open about:profiles. The file is called History in Chromium browsers, places.sqlite in Firefox and History.db in Safari.

3. Copy it somewhere easy

   Copy the file to your Desktop or Downloads folder. Working on a copy means the browser never sees a change, and you can open the viewer while the browser runs again.

4. Drop the copy here

   Drag the file onto the box above, or click it and choose the file. The viewer detects which browser it came from and lists every page with its title, address, visit count and last visit.

5. Search, filter and export

   Type words to search titles and addresses, pick a date range or a site, and sort by latest or most visited. Then export CSV, a bookmarks file or a plain list of links, or tick pages and open them.

What Happens to Your History File Here

Nothing leaves your computer. The file you choose is read into this tab’s memory and opened with sql.js, which is the SQLite database engine compiled to WebAssembly. The engine itself (about 650 KB) is downloaded from belaytab.com the first time you open a file; after that, every query runs locally on your own processor. There is no upload request, no analytics on what you open, and nothing is written to storage. Close or reload the tab and the data is gone.

History is sensitive. It shows where you bank, what you search for and which accounts you use. That is why this viewer only asks for the one file, reads only the columns it needs (address, page title, visit count and visit times), and never touches cookies, passwords or form data, which live in separate files anyway. You can check this yourself: open your browser’s developer tools, switch to the Network tab and load a file. You will see no request carrying your data.

The viewer never changes the file. SQLite opens it read-only in memory, so even if you drop the live file instead of a copy, nothing is written back to disk. Working from a copy is still the safer habit, because a browser that is running may be halfway through writing to it.

If you’re looking at history on a shared or work computer, check that you’re allowed to. The viewer can’t tell whose file it is.

Where Is the Chrome History File (and Other Browsers)?

Every desktop browser keeps history in a SQLite database inside your profile folder. Chromium browsers name it History with no extension. If you use more than one profile, replace Default with the profile’s folder name, such as Profile 1 or Profile 2. The quickest way to find the right folder is to type chrome://version into the address bar (or edge://version, brave://version) and copy the “Profile path” line. Opera shows the same path at opera://about, and Firefox lists its profile folders at about:profiles.

• On Windows, paste the path into the File Explorer address bar. %LOCALAPPDATA% and %APPDATA% expand to your own AppData\Local and AppData\Roaming folders.
• On macOS, the Library folder is hidden. In Finder, choose Go, then Go to Folder, and paste the path without the file name.
• Safari’s folder is protected by macOS privacy controls. If Finder or Terminal can’t copy History.db, give the app Full Disk Access in System Settings, then Privacy & Security, then copy the file to your Desktop.
• On Linux, the folders start with a dot and are hidden. Press Ctrl+H in most file managers to show them.

What Is a Chrome History File?

A Chrome history file is a SQLite database named History that Chrome, and every browser built on Chromium, keeps in your profile folder. It is what chrome://history reads when you press Ctrl+H. It is not a text file, which is why it looks like gibberish in Notepad and why it has no extension. You need something that speaks SQLite to read it, such as this viewer or a database browser.

Inside, two tables do most of the work. The urls table has one row per address, with the page title, how many times you visited it, how many times you typed it, and when you last visited. The visits table has one row per visit, pointing back to a row in urls, with the exact time and how you got there (a link, a typed address, a reload, a redirect). Other tables hold search terms you typed into the address bar, downloads, and clusters that Chrome uses for its Journeys view.

Times in the Chrome history file are not ordinary dates. They are counted in microseconds since 1 January 1601 UTC, the same epoch Windows uses for file times, often called WebKit time. A value such as 13434381296000000 means 20 September 2026 at 12:34:56 UTC. The viewer converts these for you and shows them in your local time; the CSV export includes both local time and UTC.

Firefox keeps the same kind of information in places.sqlite, which also holds your bookmarks. Pages live in moz_places and each visit is a row in moz_historyvisits. Firefox counts time in microseconds since 1 January 1970, known as PRTime. Safari uses History.db, with pages in history_items and visits in history_visits. Safari stores the page title on each visit rather than on the page, and counts time in seconds since 1 January 2001, the reference date Apple uses across macOS.

How far back the file goes depends on the browser. Chromium deletes history older than 90 days; the limit is written into the source code as kExpireDaysThreshold. Firefox has no fixed day limit and often goes back much further. Safari keeps history for up to one year by default, and you can shorten that in Safari’s General settings under “Remove history items”. If you sync, your Google account may keep a separate copy under My Activity, with its own retention setting; that copy isn’t in this file.

What You Can Do With a Browser History Viewer

The built-in history page is fine for finding one page from yesterday. A browser history viewer that reads the file directly helps when you need more than that: a filter by date, a count of visits, an export, or history from a computer you can’t sign in to any more.

• Find the tabs you lost last week. Your browser crashed or restarted, and the session didn’t come back. Set the date range to that day, sort by latest, and the pages you had open will be near the top. Tick them and press Open selected.
• Move history to a new computer. Copy the History file from the old laptop’s drive or a backup, drop it here, and export a bookmarks file. Import that into any browser on the new machine and the pages are one click away.
• Read an old backup. Time Machine, File History and most backup tools copy your profile folder. Restore just the History or places.sqlite file to your Desktop and open it here, without replacing your current history.
• See where your time goes. The top-domains summary adds up visits per site. It’s a quick, private way to check how often you really open news sites or social media, with no tracker involved.
• Keep a record for work. Researchers, journalists and support teams sometimes need to show which sources they visited and when. Filter by the site or date and export CSV for a spreadsheet.
• Check a browser you’ve stopped using. Moving from Chrome to Firefox? Chrome’s file still sits in your profile folder until you delete it. Open it here to pull out the handful of pages you want to keep.

Chrome History Viewer Compared With Other Ways

There are several ways to look at Chrome history, and each suits a different job. Here is an honest comparison.

Why Is the History File Locked or Empty?

While a browser runs, it holds its history database open and keeps writing to it. On Windows, this means the file is locked, so copying it may fail with “The action can’t be completed because the file is open”, or your browser may refuse to read it when you drop it here. Quit the browser fully, wait a few seconds, then copy the file again.

SQLite also writes changes to a side file first. Firefox and Safari use write-ahead logging, which puts the newest changes in a file ending -wal until they are merged into the main database. Chromium browsers use a History-journal file next to History. When a browser quits normally it merges these files back. If you copy the main file while the browser is still open, the newest visits may be missing from your copy. That’s why the steps say to quit first.

• “This is a -wal or -journal file”: you picked the side file. Choose the file without the suffix (History, places.sqlite or History.db).
• “Your browser couldn’t read this file”: the file is locked or your system blocked access. Quit the browser, copy the file to your Desktop, and drop the copy.
• “This SQLite file isn’t a browser history database”: you picked another database from the same folder, such as Cookies, Favicons, Web Data or cookies.sqlite. Look for History, places.sqlite or History.db.
• “The file looks damaged”: the copy was taken mid-write. Quit the browser and copy it again, or try a backup.
• Fewer pages than you expected: the browser had already deleted them (Chrome after 90 days), you cleared history, or you used a private window, which never writes to the file.

The viewer reads only the main database file. Changes still waiting in a -wal file aren’t shown, and history you cleared in the browser isn’t recoverable here.

Recover Tabs From Last Week Using History

History is the fallback when a session is truly gone. If your browser didn’t offer to restore your tabs after a crash or an update, first try the built-in options: press Ctrl+Shift+T (Cmd+Shift+T on a Mac) a few times, and check the “Recently closed” list in the history menu. In Firefox, the session files in sessionstore-backups often still hold the exact windows, and our Firefox session reader opens them.

If none of that works, open your history file here. Set the date range to the day the tabs were last open, sort by latest, and scan for the pages you remember. Tick each one and press Open selected, or export them as a bookmarks file so they’re safe while you sort through them. History won’t tell you which pages were open at the same moment or how they were grouped into windows. It only records visits. That is the gap a tab manager fills.