🔍 /

Browser History File Viewer

Forensic-grade utility to parse, analyze, and visualize exported browser history databases (SQLite) entirely client-side. Features session reconstruction, domain analytics, and SQL query mode.

User Rating 0.0 ★★★★★
Total Usage 0 times
Category Security

Click to Select or Drag 'History' File Here

Supports Chrome, Edge, Firefox, Safari SQLite DBs

Total Records
0
Top Domain
-
Busiest Hour
-
Last Visit
-
Showing 0 rows
Visit Time Domain Page Title Visits
No data loaded. Upload a file or try Demo Mode.
Is this tool helpful?

Your feedback helps us improve.

★ ★ ★ ★ ★

About

This tool is a specialized forensic utility designed to parse SQLite databases used by modern web browsers to store user activity. Unlike standard history managers, this viewer accesses the raw History or places.sqlite files directly from the disk, bypassing the browser interface to reveal metadata, timestamps, and access patterns often hidden from the user.

Processing occurs strictly client-side via WebAssembly (wasm). Your data is parsed in your browser's memory sandbox and never transmitted to any server. This ensures total privacy while analyzing sensitive browsing artifacts.

Key applications include digital forensics, self-auditing, and recovering lost session data. The tool automatically detects schema differences between Blink (Chrome, Edge, Brave) and Gecko (Firefox) engines, creating a normalized dataset for analysis.

forensics sqlite browser-history chrome firefox privacy

Formulas

Browser timestamps vary by engine. Chrome and Edge use the WebKit epoch (microseconds since 1601), while Firefox uses standard Unix microseconds. The conversion logic used in this tool is:

{
tunix_ms = twebkit1000 − 11644473600000 (Chrome)tunix_ms = tprtime1000 (Firefox)

Where twebkit is the raw integer value from the SQLite urls table.

Reference Data

BrowserOSTypical File PathTimestamp Epoch
Google ChromeWindows%LOCALAPPDATA%\Google\Chrome\User Data\Default\HistoryWebKit (1601-01-01)
Google ChromemacOS~/Library/Application Support/Google/Chrome/Default/HistoryWebKit
Mozilla FirefoxWindows%APPDATA%\Mozilla\Firefox\Profiles\<profile>\places.sqlitePRTime (1970-01-01)
Mozilla FirefoxmacOS~/Library/Application Support/Firefox/Profiles/<profile>/places.sqlitePRTime
Microsoft EdgeWindows%LOCALAPPDATA%\Microsoft\Edge\User Data\Default\HistoryWebKit
SafarimacOS~/Library/Safari/History.dbCFAbsoluteTime (2001-01-01)

Frequently Asked Questions

Refer to the Reference Table above. Generally, on Windows, it is in the "AppData/Local" folder for your specific browser. The file is usually named "History" (no extension) for Chrome/Edge or "places.sqlite" for Firefox. You must close the browser before uploading, as the database is locked while the browser is open.
No. This tool uses "sql.js" (SQLite for WebAssembly) to read the file entirely within your browser's memory. No data leaves your device.
The most common reason is that the browser is still open, locking the database file. Close the browser completely and try again. Alternatively, copy the "History" file to your Desktop and upload the copy.
Generally, no. When history is "cleared" in the browser, the rows are usually removed from the SQLite database immediately. However, if the database has not been "vacuumed" (compacted), raw artifact traces might remain in the binary file, but this tool visualizes only active records.