Firefox profile recovery

Firefox stores bookmarks, downloads, and browsing history in places.sqlite, with backups and other profile data stored separately.

A Firefox profile contains places.sqlite for bookmarks, downloads, and history, plus bookmark backups, favicons, sessions, preferences, extensions, saved-login files, and site data. Starting Firefox against a damaged profile can create replacements or trigger database recovery.

Understand the symptom

places.sqlite is central, but a usable browser profile depends on several independent stores.

WHY

What is happening

Mozilla documents that places.sqlite contains bookmarks, download records, and history, while bookmarkbackups stores restorable bookmark snapshots and key4.db plus logins.json form a paired credential set.

What you may see

Symptoms that change the recovery path.

01

Bookmarks and history are empty

A new profile may be selected or places.sqlite may be replaced.

02

Database disk image is malformed

SQLite pages or transaction sidecars are inconsistent.

03

Firefox created a new profile

profiles.ini or install association may point elsewhere.

04

Bookmarks restore but favicons or history do not

Different stores and backup scope explain the partial result.

Protect the source

Actions that can make the situation worse.

01

Firefox Refresh moves or replaces profile data

Preserve the original folder before using it.

02

Deleting places.sqlite loses history

Firefox may rebuild bookmarks from backup but not full browsing history.

03

Credential files must remain paired

Password data cannot be validated from logins.json alone.

Do this now

Safe steps before evaluation.

01

End every Firefox process

Prevent SQLite, session, preference, and sync writes.

02

Copy all profile folders

Keep the profile root plus profiles.ini and installs.ini associations.

03

Preserve SQLite sidecars

Keep WAL, SHM, and journal files beside each database.

04

Inventory alternate sources

Collect bookmark backups, Sync endpoints, old profiles, snapshots, and system backups.

NEPFOSYS process

How a data-first evaluation proceeds.

01

Profile mapping

NEPFOSYS identifies active and older profiles, SQLite stores, sidecars, backups, sessions, and encryption dependencies.

02

Record extraction

Readable bookmarks, history, downloads, and sessions are exported from protected copies.

03

Profile-data validation

Folders, URLs, titles, dates, counts, sessions, and expected profile identity are checked.

A clear next step

Preserve the original device before another repair or recovery attempt.

Start a case with the exact symptoms, incident timeline, prior attempts, encryption details, and the files that matter most. NEPFOSYS will route the case to the appropriate DFW intake or nationwide mail-in path.

Start with a case review

Questions, answered

What customers ask before starting.

Will deleting places.sqlite fix Firefox?

Firefox may create a new file, but the original history is then unavailable to the live profile.

Are bookmark backups a full history backup?

No. They preserve bookmarks, not every history, download, session, or profile record.

Why preserve WAL files?

Recent committed SQLite changes may still reside in transaction sidecars.

DFW local · Nationwide mail-in

Protect the device. Start with the facts.

Start my recovery case