SOURCE-CHECKED GUIDE · WEB RESEARCH
Import an HTML bookmark file into Chrome without losing track of it
Bring an HTML bookmark file into Chrome and find the imported collection, including when the browser already has bookmarks.
Chrome can import bookmarks from an HTML file. To keep track of the result, note whether Chrome already has bookmarks, then look for familiar titles and open a few links. Chrome Help says imported items appear in Other bookmarks when Chrome already has bookmarks; its Chromebook instructions mention an Imported folder. Use those locations as starting points rather than expecting the same folder label on every device.
-
Locate the HTML bookmark file exported from the other browser. Check its filename so you can distinguish it from any earlier exports. If your bookmarks are still only in the other browser, export them to an HTML file first; that browser’s export steps are outside this guide. Keep the file available until you have verified the result in Chrome.
-
Notice whether Chrome already contains bookmarks. This affects where you should look afterward: Chrome Help directs users who already have bookmarks to Other bookmarks. You do not need to reorganize anything before starting. Just remember your starting point so you can interpret what you see after the import.
-
In Chrome, use Import bookmarks and settings. Select the HTML bookmark file you identified in step 1 and complete the import. Google documents HTML files as a source for importing bookmarks. If several exports have similar names, check the filename at selection time. Choosing a different export could leave you looking for bookmarks that were never in that file.
-
Find the result. If Chrome had bookmarks before the import, check Other bookmarks first. On a Chromebook, look for the Imported folder described in Chrome Help. Look through the bookmarks there for titles you recognize from the other browser. The folder name tells you where to begin; familiar entries tell you whether you found the collection you intended to add.
-
Inspect a small sample. Choose a few recognizable bookmarks, ideally ones whose destinations you remember. Open them and check that they lead where you expect. Checking several entries helps distinguish the intended import from an older collection with a similar name. It confirms only the entries you inspected, so do not take a small sample as proof that every bookmark in a large file is present.
Use this checklist before you put the HTML file away:
- The file selected for import was the intended HTML export.
- Recognizable titles appear in Chrome, starting with the documented location that fits your situation.
- A few representative links lead to the destinations you expected.
If you see no recognizable titles, check the applicable documented location carefully before running the import again. On a Chromebook, include the Imported folder in that check. If the titles appear to belong to a different collection, revisit the HTML file you selected. If a title is present but one link leads somewhere unexpected, compare that link with the original bookmark. A bad destination on one sampled link does not, by itself, show that the whole import is missing.
When the source browser is Firefox, check the file type before importing. Mozilla distinguishes HTML export from its JSON/JSONLZ4 restore backup. If your file is a Firefox backup, return to Firefox and make an HTML export; changing the extension would not convert the contents into an HTML bookmark file.
Documentation check: Chrome Help, Mozilla Support, reviewed September 29, 2026. The menu paths and feature limits come from these pages; the result checks are steps for the reader. This workflow was not run in a live product profile. Check the current interface and your saved result before relying on either.
This guide explains a workflow using the linked primary sources. We did not independently run every step or verify the result for your files; check the current service screen and your own output.
Primary sources: