Export Chrome bookmarks: check the HTML before moving browsers

Chrome exports bookmarks as an HTML file you can open, read, and import into another browser. That makes it possible to check the saved collection before you give up access to the old computer or profile. You can see the folder names and the actual destinations of the links without signing in.

The example here is a real Chrome export containing eight public help-page links. It preserved every title, URL, and nested folder when imported into another empty Chrome profile. You can use the same files to practice a move without putting personal bookmarks into an unfamiliar browser.

Export from the profile that holds your bookmarks

Start in the Chrome profile where you normally use the collection. Work and personal profiles can hold different bookmarks even on the same computer. Google’s profile guide explains that bookmarks, history, passwords, and settings are separated by profile.

Open a familiar folder or find a recently saved link in Bookmark Manager. If it is missing there, switch to the profile where you saved it before exporting. An export from an empty profile cannot recover bookmarks stored in another one.

On desktop Chrome:

1. Open the main three-dot menu, then Bookmarks and lists, then Bookmark Manager.
2. In Bookmark Manager, open its own three-dot menu and choose Export bookmarks.
3. Save the HTML file somewhere you can access from the destination computer.

The second menu is inside Bookmark Manager. Google’s export instructions describe that distinction. In the Korean interface used for this test, the manager menu was labeled 정리 and the export item 북마크 내보내기. Your interface may use English labels.

What the exported HTML contains

The tested export was 2,317 bytes. That small file held eight links in five user folders, with the folders still nested beneath one another. It contained the titles and URLs, rather than the content of the eight linked webpages.

Here is a fragment from the actual Chrome export, with date attributes omitted to make the structure easier to read:

<DT><H3>Browser moving &amp; recovery</H3>
<DL><p>
    <DT><H3>Chrome</H3>
    <DL><p>
        <DT><A HREF="https://support.google.com/chrome/answer/96816?hl=en">Import &amp; export Chrome bookmarks</A>
    </DL><p>
</DL><p>

H3 holds a folder name. The nested DL sections contain its children. A HREF holds the bookmark’s destination, and the text inside A is its title. You do not need to understand the rest of the HTML to compare a saved URL with the one you intended to transfer.

The ampersand in Browser moving & recovery is HTML escaping. The visible folder name is Browser moving & recovery. The export also retained the ?hl=en query in the Google Help URL; it did not reduce the address to the site’s home page.

Chrome added a Bookmarks bar wrapper and ADD_DATE attributes to this export. The wrapper accounts for an additional folder heading in the file, so counting every H3 would give more than the five user folders in the input. Count A HREF entries when you are checking the number of saved links. Dates in the HTML do not prove that the linked pages themselves are current.

Open the file before importing it

Opening an export in a browser displays a local page of links. It lets you inspect the collection, but it does not add those links to that browser’s bookmarks. Adding them requires the destination browser’s import command.

You can also open the file in a text editor. Search for a distinctive title or part of its URL, such as 96816, to locate the corresponding entry. Compare the full destination address, especially if several links have similar titles. A bookmark called “Project notes” tells you less than the actual address it opens.

Keep the original export unchanged. If you want to annotate the file or remove a few links by editing HTML, work on a copy. A .html extension alone does not establish that a file contains bookmark records; the folder and link markup inside is what you are inspecting.

Practice with eight public browser-help links

Save the practice bookmark HTML to a file before choosing it in an import dialog. It contains these real folders:

• Browser moving & recovery / Chrome: four links covering import and export, creating bookmarks, Chrome profiles, and reading pages later or offline.
• Browser moving & recovery / Firefox / HTML transfer: two links covering Firefox HTML export and import.
• Browser moving & recovery / Firefox / Backup recovery: two links covering bookmark backup restoration and missing-bookmark recovery.

The matching JSON data exposes the same titles, URLs, and nested folders in another readable format. Choose the HTML file for Chrome import. The JSON download is a data reference, not a Chrome bookmark import file.

After importing the practice HTML into a separate empty profile, export it through Bookmark Manager. Look for the same eight destination URLs and the nested Firefox folders in the resulting file. This gives you recognizable items to compare with the Chrome-produced example.

Check the destination before retiring the old profile

The native export was imported into a second empty, unsigned-in Chrome profile. All eight exact titles and URLs survived, and every user-folder path matched the input. The result screenshot shows the top folder after that import.

For your own move, locate a nested folder and open a bookmark whose destination you recognize in the new browser. A file that opens correctly on disk still needs to be accepted by the destination’s importer. Keep the old profile and export available until you have found the transferred collection there.

Firefox’s HTML import instructions say that imported bookmarks are added to existing ones under the Bookmarks Menu. That is documented destination guidance; the test here was Chrome to Chrome. Firefox, Edge, mobile browsers, and synchronization were not tested.

Your personal export can expose private titles and URLs. The downloadable examples here contain only the eight public Google and Mozilla help links.

Source and test scope: Chrome export help, bookmark management help, and the linked destination documentation were checked October 7, 2026. The native test used Chrome 154.0.8037.93 on Windows, in Korean, with two new unsigned-in profiles. No personal collection was used.