Firefox Bookmarks Disappeared: How to Restore Them

You opened Firefox this morning and your bookmarks were not there. The strip under the address bar is empty, or the whole sidebar looks like a fresh install, and you know for certain you did not delete anything. Yesterday there were hundreds of saved links. Today there is nothing, and no message explaining where they went.

Firefox is the best browser to have this happen in. That sounds like a strange thing to say while you are staring at an empty bookmark list, but it is true, and it changes what you should do next. Chrome keeps exactly one backup file and overwrites it the next time it saves. Firefox keeps fifteen dated ones, automatically, and has done for years.

So the question in front of you is not “can I get them back”. It is “which day do I want them from”. That is a much smaller question, and you do not need to rush it. Nothing is ticking down while you read this.

This guide is for bookmarks that vanished on their own. If you know you deleted a folder and want it back, that is a different problem with a different fix, and it lives in recover deleted bookmarks. Everything below was checked against Firefox’s own source code and preference files on August 3, 2026, against Firefox 153.0.1, the current release.

Why did my Firefox bookmarks disappear?

There are five real causes and they are nowhere near equally likely. Two of them involve no data loss at all, and one of them means Firefox has already fixed the problem without telling you.

Work down that list in order. People skip to the bottom, decide they have lost everything, and start downloading disk recovery software for a problem that a keyboard shortcut would have solved. Look at what currently ranks for this search and a good chunk of it is exactly that software, which tells you more about the money in data recovery than about the difficulty of the problem.

Are they hidden rather than gone?

Press Ctrl+Shift+B on Windows and Linux, or Cmd+Shift+B on a Mac. If a row of links reappears instantly, nothing was ever missing.

This is worth checking first because of a default almost nobody knows about. Firefox ships with browser.toolbars.bookmarks.visibility set to "newtab", which you can read for yourself in Firefox’s own preference file. That value means the bookmarks toolbar appears on the new tab page and nowhere else.

Think about what that produces. You open a new tab, see your bookmarks, and assume they are always there. You click a link, land on a real page, and the row silently disappears. Do that a few hundred times and the toolbar becomes a thing that flickers in and out of existence, until one day you notice it is missing on the page you are looking at and conclude your bookmarks are gone.

Right click the toolbar area and you get three choices. Always Show, Never Show, and Only Show on New Tab. Pick Always Show and the flickering stops for good. Chrome has the identical problem with the identical shortcut, which is why a hidden bookmarks bar earns its own guide over there too.

While you are here, open the Library with Ctrl+Shift+O and look at the sidebar. Bookmarks saved without picking a folder land in Other Bookmarks, not on the toolbar. A toolbar that looks thin can be sitting above hundreds of saves you forgot were there.

Did Firefox open a different profile?

Type about:profiles into the address bar. You will see every profile on the machine, which one is in use, and a Root Directory path for each.

If there is more than one listed, launch the other one and look. A Firefox profile is a folder holding one complete set of bookmarks, history, passwords, and extensions. Two profiles are two separate browsers wearing the same icon, and switching between them looks exactly like data loss.

This cause is getting more common rather than less, and there is a specific reason. Firefox’s built-in profile manager was a staged rollout that reached everyone on the release channel from October 14, 2025, and browser.profiles.enabled is now true by default in the source. Multiple profiles used to be a power-user feature you had to go looking for. Now there is a menu for it, which means far more people can create a second one without quite meaning to. Mozilla’s own profile management guide covers the switching.

Two situations deserve their own mention. On Linux, the Snap, Flatpak, and distribution packages of Firefox each store their profile in a different place, so switching install method leaves your old profile intact and unreachable from the new one. And after a reinstall on any platform, check about:profiles before you conclude anything, because a fresh profile with a fresh name is the usual outcome.

What Firefox’s automatic backups actually are

Here is the part that makes Firefox different, and the part most guides describe vaguely.

Inside your profile folder there is a directory called bookmarkbackups. Firefox writes a compressed JSON file into it, named like this.

bookmarks-2026-08-01_412_kR4qL2vXhQ8=.jsonlz4

Three pieces of information sit in that filename, and the code that builds it spells out what each one is. The date. The number of bookmarks in that backup. And a hash of the contents.

That middle number is the useful one and almost nobody points at it. You can open the bookmarkbackups folder in your file manager and read, at a glance, how many bookmarks each day held. If Friday says 412 and Monday says 3, you know exactly which day things went wrong and exactly which file to restore, without restoring anything blind to find out.

Three rules govern that folder, all readable in the same file.

• Fifteen is the cap: browser.bookmarks.max_backups defaults to 15, and the oldest is deleted when a sixteenth arrives.
• One per date: if a backup already exists for today, the new one replaces it rather than stacking up.
• Only when something changed: Firefox compares a content hash against the most recent backup and skips writing if they match.

That third rule has a consequence worth knowing. Fifteen backups do not mean fifteen days. They mean the last fifteen days on which your bookmarks actually changed. If you save links in bursts and then leave them alone for a month, your oldest backup can be from well before last month, which is better coverage than the number suggests.

How to restore from a dated backup

Press Ctrl+Shift+O to open the Library. Click Import and Backup, then Restore, and a list of dated backups appears. Pick one.

One warning, and it is the one that turns a recovery into a second loss. Restoring in Firefox replaces your entire bookmark set with the backup. It does not merge. Anything you saved after that backup date is gone the moment you confirm.

So do this first, every time. In the same Import and Backup menu, choose Export Bookmarks to HTML and save the current state somewhere outside the profile folder. It takes five seconds. If the restore brings back the wrong day, or brings back less than you hoped, that HTML file is your undo button. Without it there is no undo button.

If the backup you want is not offered in the list, use Choose File in that same Restore menu and point it at the .jsonlz4 file directly. That matters when you are pulling a profile off an old machine or out of a backup drive, because Firefox will happily restore a file from a profile that is not the one you are running.

Did Firefox already restore them for you?

This is the cause nobody explains, and it is the answer to the most confusing version of this problem. Your bookmarks are there, but they are a few days out of date, and you have no idea why.

Firefox stores bookmarks and history together in a single database file called places.sqlite. When it opens that file and finds it damaged, the recovery is automatic and completely silent. It renames the broken file to places.sqlite.corrupt and builds a fresh empty one, and it will only write one corrupt file per 24 hours, so that a repeating fault cannot quietly fill your disk.

Then, at startup, Firefox works down a ladder. It notices the database is new or corrupt. It looks for your most recent backup and imports it. If there is no backup, it looks for a bookmarks.html file in the profile. If there is no HTML file either, it gives up and installs the factory default bookmarks.

That last rung is a distress signal, and reading it correctly saves you an hour. If you are looking at the starter bookmarks that ship with a brand new Firefox, that folder of Mozilla links, the recovery ladder reached its bottom step. Firefox did not merely lose your bookmarks. It looked for a backup, found none, looked for an HTML export, found none, and reset. That is the one version of this where you should stop clicking and go find an older copy of the profile folder.

The much more common outcome is the happy one. Firefox found a backup from three days ago, restored it without a word, and now you are missing exactly the links you saved this week.

Why your history vanished with your bookmarks

Notice what the backups do not cover.

places.sqlite holds bookmarks and history in one file. The bookmarkbackups folder holds bookmarks and nothing else. So when that database gets rebuilt, the recovery ladder hands your bookmarks back and your entire browsing history is simply gone. There is no dated history backup to restore from, because Firefox never made one.

That asymmetry is the real data loss in this whole scenario and it goes almost entirely unmentioned. People spend an afternoon relieved that their bookmarks came back, and never register that months of history left the building at the same moment. If you rely on typing three letters in the address bar to find things you read once, that habit just stopped working and nothing told you why.

What if Firefox Sync is the problem?

Open the account menu and check whether you are actually signed in. Signing out of Firefox Sync leaves the local bookmarks alone, but signing into a different account, or into a fresh profile that then syncs, shows you that account’s set instead of yours.

The more important point is one that applies to every browser. Sync is not a backup. Its job is to make your devices agree with each other, which means deleting a folder on your laptop deletes it on your phone within seconds, on purpose, with no server-side undo. It is the fastest way to lose the same bookmarks twice, and it is why sync was never the safety net people treat it as.

If your bookmarks are missing on every device at once, sync did what it was told. Go to the dated backups on the machine where the deletion happened.

The one setting worth changing today

browser.bookmarks.autoExportHTML defaults to false. You can see it sitting there in the same preference file as the backup cap.

Turn it on. Type about:config, accept the warning, search for that name, and set it to true. Firefox will then write a plain bookmarks.html file into your profile every time it shuts down.

Why bother when there are already fifteen backups? Because those backups are compressed JSON that only Firefox can read, stored inside the profile folder, which is exactly the folder that gets lost when a profile gets lost. A bookmarks.html file opens in any browser and any text editor. It is also the second rung on that recovery ladder, so having one means Firefox has somewhere to fall when the backups are missing.

Better still, copy that HTML file somewhere outside the browser once a month. That single habit turns every scenario on this page into a five minute annoyance, and it is the same move that makes moving bookmarks between browsers painless.

The saves this fix never reaches

Everything above works because Firefox bookmarks are files on your machine. You can open the folder. You can count them from a filename. That is the entire reason this problem has a happy ending.

Now think about the rest of what you save. The X threads you bookmarked mid-scroll. The Reddit posts you tapped save on. The LinkedIn updates you kept for later. There is no profile directory for those, no dated backup folder, no export button worth the name. When one of those platforms changes its mind, or the original poster deletes their account, your save becomes a dead link and no recovery ladder runs.

That gap is why I built ContextBolt, so read this part knowing the bias. It is a Chrome extension that captures what you save on X, Reddit, and LinkedIn into one collection, storing the content of each post rather than just a link to it. AI tags each save, and search works by meaning, so “that thread about pricing psychology” finds the thread even when you cannot remember a single word of it.

Basic is free and covers 150 saves. Pro at $6 a month makes it unlimited, adds encrypted cloud sync, and gives you an MCP endpoint so Claude or Cursor can read your saves inside a conversation. It does nothing for your Firefox bookmarks, which are fine, and it is not what you came here for.

The honest take

Firefox handles this better than any other browser and still manages to make it frightening.

Fifteen dated backups is a genuinely good design, made by somebody who understood that people lose things. The silent auto-restore is good too. Rebuilding a broken database and quietly refilling it from Friday’s copy is the correct behavior, and most users would rather it just happened.

What is missing is one sentence. Firefox knows it found a corrupt database. It knows which backup it restored and what date that backup carries. It could say “your bookmarks were restored from August 1 and your history could not be recovered” in a bar across the top of the window, and the entire panic this page exists to answer would evaporate.

Instead it says nothing, and the user is left to conclude that the browser ate their data. Which is how a SERP for a solved problem fills up with recovery software, forum threads from 2019, and paid experts answering a question that a keyboard shortcut answers for free.

Press Ctrl+Shift+B. Check about:profiles. Then go read the numbers in your backup filenames. The answer is almost always sitting right there.