Skip to content

Browser Forensics Tool Selection Guide

Choose your investigation

Match the evidence to the question.

Start with the question and acquired browser format. Choose one primary viewer, then use another source to test the finding. For concepts and the existing browser exercise, see Understanding Browser Forensics.

Start withA question and an acquired profile
ChooseOne primary viewer for the source
Finish withA result you can corroborate

Choose by investigation

Compare all tools and supported formats
Compare the options and their limits
Your questionStart hereTools and format fitCheck before relying on it
Which sites appear across profiles?History, searches and bookmarksBrowsingHistoryView: supported Chrome, Firefox, Edge, IE and Opera historyPreserve the browser/profile and source file per row; merged output is not one person's activity.
Which visits are recorded in this Chrome profile?Chrome historyChromeHistoryView: Chrome and supported Chromium historyRecord version and file selection; a URL may come from redirects or synchronisation.
What does this Firefox history contain?Firefox historyMZHistoryView: places.sqlite and legacy Mozilla historyConfirm format and time handling; merged URL summaries are not individual visits.
Are search terms or saved links present?Searches and bookmarksMyLastSearch: recognised query URLs; FavoritesView: supported IE/Mozilla bookmark formatsBoth need compatibility checks. A saved link is not a visit; missing search output is not proof of no searches.
What was downloaded and where?Download analysisBrowserDownloadsView: Chrome/Firefox, with documented Chromium variantsCompare state, target path and times with the retained file and NTFS records.
What site state survives in this profile?Cookies and sessionsChromeCookiesView: Chrome cookie data; MZCookiesView: supported Firefox/Mozilla cookie filesCookie values can be encrypted or sensitive. Presence does not establish successful login or an actor.
Which resources remain cached?Cache and imagesChromeCacheView: Chrome/compatible Chromium; MZCacheView: Firefox/Mozilla cacheChoose the actual acquired cache directory, not the analyst's default profile.
Can I review cached images or EXIF?Image reviewImageCacheViewer: supported cache images; WebCacheImageInfo: cached JPEGs containing EXIFImage retrieval is not proof of deliberate viewing; EXIF creation time is not browser visit time.
I have older Safari artefactsLegacy ToolsSafariHistoryView: History.plist; SafariCacheView: cache.dbNo blanket claim of current Safari/macOS/iOS support. Identify the file format first.

Browser support above is the author's documented scope, checked on 27 October 2026, not certification against every current browser build. Each category links to the publisher's format/version notes. Record the viewer and browser versions and validate a known record on your own training profile.

Prepare once, reuse across tools

Prepare sources and tools before examination
  1. Identify the sourceRecord the host, account, browser version, profile path and time zone.
  2. Acquire a consistent setKeep database companions and folder structure. Follow a validated method for live evidence; a changing profile may copy inconsistently.
  3. Keep an unchanged sourceExamine a working copy. Record paths and SHA-256 hashes; save exports separately.
  4. Prepare the viewerUse official downloads or an approved SUSA build. Extract to C:\Tools\<ToolName>; record the version and executable hash.
  5. Load, check and exportSelect the working source. Check unfiltered records, then export with headers, settings and time notes.
Troubleshoot an empty result

Check the selected profile and input filename, browser format, date range, time conversion, locks, SQLite companions and parser version. Widen filters and compare with a known training action. A successful launch or an empty table does not establish compatibility or absence of activity.