To understand where Chrome bookmarks live, one must first understand the browser’s underlying structure. Chrome is built on the Chromium open-source project, which treats each user profile as a distinct, sandboxed entity. This means your bookmarks are not stored in the application folder (e.g., "Program Files" on Windows or the "Applications" folder on macOS) but within a user-specific data directory. This design is intentional: it allows multiple people using the same computer to have separate, private bookmark collections without interference.
Yet, the location of Chrome bookmarks also reveals a subtle tension in modern computing. On one hand, storing bookmarks as a local JSON file aligns with the classic Unix philosophy of small, transparent, manipulable text files. On the other hand, Google would prefer you never touch this file. The company’s entire ecosystem—Chrome Sync, the Bookmarks Manager, the mobile app—encourages users to treat bookmarks as an ethereal cloud entity. The local file is a legacy implementation detail. But for those who have lost years of curated links to a sync error or a forgotten password, the humble Bookmarks file in the hidden AppData folder becomes a symbol of resilience: a local copy that no server can revoke. chrome bookmark location
The canonical location varies by operating system, a fact that often frustrates users migrating between platforms. On , the path is typically C:\Users\[YourUserName]\AppData\Local\Google\Chrome\User Data\Default\Bookmarks . The AppData folder is hidden by default, a digital curtain drawn to prevent accidental modification. On macOS , the pilgrim must navigate to ~/Library/Application Support/Google/Chrome/Default/Bookmarks , with the Library folder similarly concealed. For Linux users, the trail leads to ~/.config/google-chrome/Default/Bookmarks . In each case, "Default" represents the primary user profile; secondary profiles reside in folders named "Profile 1," "Profile 2," and so on. To understand where Chrome bookmarks live, one must
Herein lies the first revelation: the Chrome bookmark is not a database or a complex registry entry, but a plain-text (JavaScript Object Notation). If you open this file with a text editor, you will not see icons or thumbnails but a hierarchical, human-readable structure. The file contains two main roots: "bookmark_bar" (the bookmarks visible below the address bar), "other" (the "Other bookmarks" folder), and "synced" (for mobile or other synced devices). Each entry includes a name, a URL, a date-added timestamp, and a unique ID. This JSON format is a stroke of genius for portability—it can be read, edited, or scripted by any programmer—but it is also fragile. A single misplaced bracket can corrupt the entire bookmark collection. This design is intentional: it allows multiple people
Second, : When moving to a new computer or switching browsers (to Firefox, Edge, or Brave), the import/export tool is convenient but often incomplete, losing folder structures or favicons. Directly copying the Bookmarks JSON file from the old User Data folder to the new one is the most complete form of migration. Similarly, power users who dual-boot Windows and Linux can symlink (create a symbolic link) the bookmark file from a shared partition, maintaining the same collection across operating systems.