TESTED · WEB RESEARCH
Chrome bookmarks imported but missing? Find the folder and avoid duplicates
Find bookmarks after a Chrome HTML import and diagnose duplicated folders, with real empty-profile and repeat-import results plus a practice file.
If Chrome finished importing bookmarks but you cannot see the links, check the profile and search Bookmark Manager for a title from the file. A collection can be hidden several folders below the bookmarks bar. Importing the file again can create another copy of the same collection.
That happened with the eight-link practice file here. The first import added eight links. A second import added eight more, and a search for one title showed two matching entries. The original folder stayed in place. Finding it would have avoided the duplicate import.
Check whether the file was actually imported
Opening a bookmark HTML file in a browser displays its saved links as a webpage. Those links are still in the file; opening it does not add them to Chrome’s bookmarks.
Google’s documented desktop import path is the main three-dot menu, Bookmarks and lists, Import bookmarks and settings, Choose file, Open, then Done. Select the bookmark HTML file you saved from the other browser.
The native test used Bookmark Manager’s own three-dot menu and its Import bookmarks command. The interface was Korean: the manager menu was 정리, the import item 북마크 가져오기, and the Windows file picker opened with an Open button. These were actual menu actions in a new profile, not a preloaded bookmark collection.
If you only opened the HTML as a page, use the import command once. If you already completed an import, look for its result before selecting the file again.
Check the contents, not just the extension
A bookmark HTML export contains destination URLs in A HREF entries. You can open a copy in a text editor and search for a familiar domain or title. For example, the practice collection contains:
<A HREF="https://support.google.com/chrome/answer/96816?hl=en">Import & export Chrome bookmarks</A>
The & becomes an ampersand when displayed. The bookmark’s visible title is Import & export Chrome bookmarks. Search for that readable title in Chrome, rather than copying the HTML tag into the search box.
For Firefox bookmarks, use Export Bookmarks to HTML. Firefox’s JSON backup and Restore procedure is a separate workflow; Restore replaces the current Firefox bookmark set. Renaming a .json or .jsonlz4 file to .html does not convert its contents into HTML bookmark records.
The practice HTML and matching JSON data contain the same eight public links, but serve different purposes. Save the HTML to a file for Chrome import. Use the JSON to inspect the collection’s titles and nested structure. The JSON is not the file to choose in Chrome’s HTML import dialog.
Make sure you are looking in the same profile
Chrome profiles keep separate bookmarks. An import in a work profile will not be visible just because you open the same Chrome application in a personal profile.
Check the profile used when you imported the file, then open Bookmark Manager there. If you want to practice first, Google’s profile guide explains how to add a separate Chrome profile. The downloadable collection contains only public help links, so there is no need to experiment with your personal bookmarks.
The absence of a link in another profile does not establish that the import deleted it. Check the destination profile before changing files or deleting anything.
Find a link first, then follow the folder structure
In Bookmark Manager, search for the title of a link you know was in the file. Google’s bookmark guide also describes searching from the address bar: type @bookmarks, press Tab or Space, and enter your query.
For the practice file, search for Import HTML bookmarks into Firefox. Its folder path is:
Browser moving & recovery
Firefox
HTML transfer
Import HTML bookmarks into Firefox
Once you know the link exists, clear the search and explore the matching collection in the folder tree. The folders in the practice file give you recognizable names to follow. Do not count only the rows visible at the root: the first import screenshot shows one top-level folder, but that folder contains all eight links across five nested user folders.
Google’s general import guidance says an empty Chrome collection receives bookmarks on the bookmarks bar, while an existing collection receives them in Other bookmarks. The Windows Chrome 154 result here differed on the second import. It added a new wrapper called 가져온 북마크, or Imported bookmarks, inside the bookmarks bar, alongside the original folder.
The repeat-import screenshot shows those two top-level folders. Search for a known link and inspect the folders you actually have; a missing Other bookmarks entry alone is not proof that the import failed.
Recognize a duplicate import before removing anything
The repeated import produced these results in the same unsigned-in profile:
| Collection state | Links in the profile | What was visible at the top level |
|---|---|---|
| Before importing | 0 | Empty bookmarks bar |
| After the first import | 8 | Browser moving & recovery |
| After importing the same file again | 16 | Original folder plus an Imported bookmarks wrapper |
Every original title and URL appeared exactly twice after the repeat. Searching for Import & export Chrome bookmarks returned two matching rows. Chrome’s stored bookmark data confirmed that both entries pointed to the same URL.

Two matching titles do not always mean an accidental copy. Compare the URLs and parent folders: a reader might deliberately keep the same page under different subjects. In this test, the later Imported bookmarks wrapper held another complete Browser moving & recovery collection. The earlier branch remained untouched.
Export the current collection before a large deletion. Identify the unwanted copied branch, inspect its links, then use Bookmark Manager’s documented delete control. Avoid deleting the original collection merely because it appeared first in search results. Deletion and undo were not tested here, and no recovery promise follows from the import test.
Source and test scope: the linked official instructions were checked October 7, 2026. The native test used Windows Chrome 154.0.8037.93, in Korean, with a new unsigned-in profile and eight public Google and Mozilla help links. The file was imported twice, with visible results checked against Chrome’s bookmark data. Mobile Chrome, synchronization, other Chrome versions, and Firefox import were not tested.