Export Chrome History to CSV or JSON
Chrome has no "export history" button. Its History page (Chrome 154) offers search, a date or group view, tabs from other devices, and Delete browsing data, but nothing that saves a file. To get a spreadsheet-ready CSV or a JSON file of your local Chrome history, copy the profile's History database and run one SQLite query on the copy. If your history syncs to your Google Account, Google Takeout is a second route.
We tested the procedure below on October 2, 2026, with Chrome 154.0.8037.59 on Windows 11 and the SQLite 3.44 command-line tool. The same query also worked on copies of the Microsoft Edge 154 and Brave 1.96 History files, because both browsers use Chromium's history format.
Step 1: Find the right profile folder
Open chrome://version in the address bar and look at the Profile Path line. That folder holds the History file for the profile you are using. Do not assume the folder is called Default: a second Chrome profile is usually Profile 1, Profile 2, and so on, and each one has its own history.
Typical locations look like this:
- Windows:
%LOCALAPPDATA%\Google\Chrome\User Data\Default\History - macOS:
~/Library/Application Support/Google/Chrome/Default/History - Linux:
~/.config/google-chrome/Default/History
Step 2: Copy the History file
Close every Chrome window, then copy History (the file has no extension) into a working folder and name the copy History-copy. Always work on the copy, never on the file Chrome uses.
In our test, querying the live file while Chrome was open failed with database is locked. Copying the live file did work, and that copy contained all eight test visits, but a copy taken while Chrome is running can miss the newest visits if Chrome has not written them to disk yet. Closing Chrome first gives you a complete, consistent snapshot.
Step 3: Get the sqlite3 tool
Download the command-line tools bundle from sqlite.org/download (on Windows, sqlite-tools-win-x64). macOS already includes sqlite3, and most Linux distributions offer it as the sqlite3 package. JSON output needs version 3.33 or newer; check with sqlite3 -version.
Step 4: Run the export script
Save this as export-history.sql in the same folder as History-copy:
.headers on
.mode csv
.once history-export.csv
SELECT
datetime(v.visit_time / 1000000 - 11644473600, 'unixepoch') AS visit_time_utc,
u.url,
u.title,
u.visit_count
FROM visits AS v
JOIN urls AS u ON u.id = v.url
ORDER BY v.visit_time;
.mode json
.once history-export.json
SELECT
datetime(v.visit_time / 1000000 - 11644473600, 'unixepoch') AS visit_time_utc,
u.url,
u.title,
u.visit_count
FROM visits AS v
JOIN urls AS u ON u.id = v.url
ORDER BY v.visit_time;Then run it from that folder:
sqlite3 History-copy ".read export-history.sql"You get two files, history-export.csv and history-export.json. Letting SQLite write the files with .once, instead of redirecting output with >, matters on Windows: Windows PowerShell 5.1 re-encodes redirected output as UTF-16, which many spreadsheet tools misread.
What the query does: Chrome stores each page once in the urls table and each visit in the visits table. The query joins them so you get one row per visit. Chrome records time as microseconds since January 1, 1601 (UTC); the datetime(...) expression converts it to a readable UTC timestamp. Replace 'unixepoch' with 'unixepoch', 'localtime' to get your computer's local time instead.
What the output looks like
This is the CSV our test produced. The pages were local test pages we created for the run, so the address is shown as 127.0.0.1:PORT:
visit_time_utc,url,title,visit_count
"2026-10-02 00:32:37",http://127.0.0.1:PORT/repeat,"Repeat visit page",3
"2026-10-02 00:32:39",http://127.0.0.1:PORT/comma,"Budget, ""Q3"" plan & notes",1
"2026-10-02 00:32:42",http://127.0.0.1:PORT/unicode,"Café 日本語 テスト",1
"2026-10-02 00:32:44",http://127.0.0.1:PORT/repeat,"Repeat visit page",3
"2026-10-02 00:32:47",http://127.0.0.1:PORT/redirect,"Redirect landing",1
"2026-10-02 00:32:47",http://127.0.0.1:PORT/landing,"Redirect landing",1
"2026-10-02 00:32:49",http://127.0.0.1:PORT/untitled,"",1
"2026-10-02 00:32:52",http://127.0.0.1:PORT/repeat,"Repeat visit page",3And one record from the JSON file:
{
"visit_time_utc": "2026-10-02 00:32:39",
"url": "http://127.0.0.1:PORT/comma",
"title": "Budget, \"Q3\" plan & notes",
"visit_count": 1
}Things worth knowing before you analyze the file:
- Repeat visits are separate rows. The page we opened three times appears three times.
visit_countis the page's total, so it reads3on each of those rows. For one row per page, group by URL in your spreadsheet or queryurlson its own. - Redirects add a row. Opening
/redirectrecorded both the redirecting address and the page it landed on, and the redirecting address took the landing page's title. - Titles can be empty. A page without a
<title>exported with an empty title. - Commas, quotes, and non-English text survive. Fields with commas or quotation marks are quoted correctly, and the file is UTF-8. Our CSV parsed into the same four columns on every row.
- The timestamps are right. Each exported time matched the moment our test server received the page request, to the second.
What the export includes and leaves out
The file contains only what is still in that profile's local History database:
- Roughly the last 90 days. Google's Chrome Help says History lists pages visited in the last 90 days. In our test, Chrome deleted visits older than 90 days from the database within minutes of starting, so an export can never reach further back than that. See how long Chrome keeps history for the details.
- No Incognito visits. Chrome does not write them to
History; in our Incognito test a page opened only in an Incognito window left no row. - No deleted visits. Anything removed with Delete browsing data is gone from the file too.
- No page text. You get addresses, titles, and times, not what the pages said.
- One profile at a time. Repeat the steps for each profile folder you care about.
The account route: Google Takeout
If you are signed in to Chrome and sync history, Google's help page on exporting your data from Chrome says you can download "Chrome browser history" along with bookmarks, autofill, extensions, and settings through Google Takeout. Use this when you want the copy held in your Google Account rather than the file on one computer. Takeout delivers an archive, not a CSV. We did not run a Takeout export for this guide, so check the files and fields in your archive before relying on them.
A built-in alternative in Edge
Microsoft Edge 154 has an Export browsing data button on its History page; Chrome does not. If you browse in Edge, see how to search Edge browsing history. For Brave, the same SQLite route works, and Brave can also keep history longer than 90 days (Brave history guide).
If you need more than a 90-day file
An export is a snapshot. To keep a searchable record past Chrome's window, repeat the export regularly, or capture pages as you browse with a tool built for it. Disclosure: TraceMind is our product. TraceMind captures the text of supported pages locally as you visit them and keeps captured history for as long as you choose, with no TraceMind page cap (browser storage still applies). Its separate Chrome-history import reaches back up to 365 days and 10,000 entries, but imports only addresses, titles, and visit times, not the text of pages you saw before installing it. For more options, see our comparison of browser history extensions.
FAQ
Can I export Chrome history without installing anything?
Not as a CSV or JSON file. Chrome's History page has no export button, so you need either the SQLite tool for the local file or Google Takeout for history stored in your Google Account.
Why does the query fail with "database is locked"?
You are querying the file Chrome is using. Close Chrome, copy History to another folder, and run the query on the copy.
Why are some pages listed several times?
The export has one row per visit. A page you opened three times appears three times; visit_count shows its total.
Can an export bring back deleted history?
No. The export contains only visits still in the database. Deleted visits, Incognito visits, and visits older than Chrome's roughly 90-day window are not there.
Does this work for Edge or Brave?
Yes. We ran the same script on copies of the Edge 154 and Brave 1.96 History files and got the same eight rows. Their profile folders are under Microsoft\Edge\User Data and BraveSoftware\Brave-Browser\User Data; use edge://version or brave://version to find the exact path.
