Convert your Pocket export
Turn Pocket's CSV into a bookmarks HTML file any browser can import, or into clean JSON. Unzip your Pocket export first — the CSV is inside.
| Title | URL | Added | Tags | Status |
|---|
What's inside a Pocket export
Short version: the file that matters is list.csv. The ril_export.html preview sits next to it and looks importable, but [we measured a genuine one against our importer: 0 of 261 bookmarks parse](/research/bookmark-import-fidelity) — it's a plain list, not the Netscape format bookmark tools read.
Pocket's final export format was a ZIP archive containing one or more CSV files (large libraries were split into parts). Each row is one save with five columns:title, url, time_added (a Unix timestamp),tags (pipe-separated), and status (unread orarchive). That's the whole inheritance — no article text, no images, no highlights. The full anatomy is inwhat's in your Pocket export file.
Unzip before uploading. This tool reads the CSV, not the ZIP. If your export came in parts, convert each CSV separately.
An honest note about timing
Pocket shut down in July 2025, and the export endpoint itself went dark onNovember 12, 2025. There is no way to generate a new export today — this page exists for the people who grabbed their file in time and still have it sitting in Downloads. If that's you, the file is fully usable: every URL, tag, and save date is intact, and converting it takes seconds. The broader migration options are covered inhow to export and migrate your Pocket data.
What each download gives you
- Bookmarks HTML — the standard Netscape format every browser imports. Save dates are preserved via
ADD_DATE, and your Pocket tags are written to theTAGSattribute (Firefox imports those; Chrome ignores the attribute but keeps the links). The list is flat — Pocket had tags, not folders, so there is no tree to lose. - JSON — every field preserved exactly, including
status, which the bookmarks format can't represent. The right choice if you're scripting a migration or want a lossless archival copy alongside the CSV.
Where to point the file next
Any browser will swallow the bookmarks HTML — but a browser's bookmark manager is a downgrade from what Pocket did. Marqly imports the Pocket file directly (no conversion needed), AI-tags and summarizes every save on the way in, and finds any of them later from a half-remembered description. Follow ourstep-by-step Pocket migration guide (or see thePocket import FAQ), and read the full feature breakdown at Pocket alternatives.
Frequently asked questions
Can I still export my data from Pocket?
No. Pocket shut down in July 2025 and the export page stopped working on November 12, 2025. This tool is for people who downloaded their export while it was available. If you have the ZIP Pocket emailed or served you, your saves are in there as CSV — unzip it and you are fine.
What exactly is in the Pocket CSV?
One row per save with five columns: title, url, time_added (a Unix timestamp), tags (separated by | pipes), and status (unread or archive). No article text, images, or highlights — Pocket exports were always just the link list plus that metadata. This tool preserves all five fields in the JSON output.
Does the bookmarks HTML keep my tags and read status?
Tags yes — they are written into the TAGS attribute, which Firefox reads on import (Chrome ignores it but keeps the links). Read status no: the bookmarks format has no concept of unread versus archived, so everything imports as a plain bookmark. Use the JSON download if the status matters to you.
Do I even need to convert it for Marqly?
The CSV, yes — import list.csv straight in (titles, URLs and tags carry; dates and status do not). The ril_export.html beside it is NOT a format Marqly reads — a real export parses to zero saves, which is exactly what this converter fixes: convert the CSV to standard bookmarks HTML here, then import that anywhere. AI tagging and summaries on import are Pro; see the <a href="/migrate/pocket">Pocket migration guide</a> for the full matrix.
