Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

Can't import Chrome bookmarks from non-Chrome .html file.

  • 1 reply
  • 1 has this problem
  • 1 view
  • Last reply by cor-el

more options

Recently, my Win 7 PC di.ed, and I replaced it with a new one. My Chrome bookmarks were not there anymore...no surprise. I did have a PC backup from before the old one died, and was able to recover the "Bookmarks" file. I saved it in .txt, .docx, and .html formats. Firefox import-from-html instructions do not add them to Firefox bookmarks. I suspect it's because of how I restored a file that was not necessarily created by Chrome. ANy halp? Many thanks

Recently, my Win 7 PC di.ed, and I replaced it with a new one. My Chrome bookmarks were not there anymore...no surprise. I did have a PC backup from before the old one died, and was able to recover the "Bookmarks" file. I saved it in .txt, .docx, and .html formats. Firefox import-from-html instructions do not add them to Firefox bookmarks. I suspect it's because of how I restored a file that was not necessarily created by Chrome. ANy halp? Many thanks

All Replies (1)

more options

Google Chrome stores its bookmarks in a Bookmarks file in JSON format that Firefox can't use directly.

You will either have to place that Bookmarks file in the original location for a Google profile folder to see if you can import them in Firefox or install Google Chrome and export the Bookmarks to an HTML file.

C:\Users\<username>\AppData\Local\Google\Chrome\User Data\Default\

There are other things that need your attention.

Your above posted system details show multiple Flash plugin(s, so you may want to look into that to decide which to keep.

  1. Shockwave Flash 10.3 r181
  2. Shockwave Flash 11.2 r202

You can set the plugin.expose_full_path pref to true on the about:config page to see the full path of plugins on the about:plugins page.

It is best not to leave that pref set to true as it exposes that full path to web servers, so reset that pref to false after you are done with the about:plugins page.

See "Manually uninstalling a plugin":