Tool Comparisons
How to migrate from Omnivore to WebSnips — a practical guide for students and researchers who used Omnivore as a free, open-source read-later tool and
Omnivore was a popular open-source, free read-later and annotation tool that attracted a following among students, researchers, and power users who wanted Readwise-style features without the subscription cost. In late 2024, Omnivore was acquired and the hosted service shut down, leaving its user base needing to migrate.
This guide covers how to migrate from Omnivore to WebSnips — preserving your saved articles and rebuilding your research organization in an actively maintained alternative.
Omnivore did well:
Why users are migrating: Omnivore's hosted service shut down in late 2024 following acquisition. While the open-source code remains available for self-hosting, most users can't or don't want to run their own server. The community has forked the project as "Hoarder" and other alternatives, but the migration question is: what to do with the archive you had on Omnivore's hosted service.
Who this migration is for: Students and lifelong learners who used Omnivore to save articles for later, annotate research, and build a knowledge library — and now need to move that content somewhere actively maintained.
Omnivore provided a good export before the hosted service shut down.
Omnivore export (while active): Account Settings → Export → Download export
What the Omnivore export includes:
What the Omnivore export does NOT include:
The self-hosting option: If you're technically inclined, you can run Omnivore's open-source code or its fork "Hoarder" and import your Omnivore export directly. This preserves everything — highlights, notes, labels. But this guide assumes you want to move to a hosted, maintained tool rather than self-host.
If you still have your export file from when Omnivore was active, proceed from there. If you don't have an export and the hosted service is no longer accessible, check your local browser history and bookmarks for recoverable URLs.
Omnivore's export is in JSON format. Each item has a url field. You need to extract these into a plain text file (one URL per line) for import into WebSnips.
Manual extraction: Open the JSON file in a text editor and search for "url": entries to collect the URLs.
The URL list is your WebSnips import file.
Use WebSnips' import to import your URL list. WebSnips re-captures the full page content of each URL.
What carries over:
What doesn't carry over:
Omnivore used labels as the primary organizational system. WebSnips uses Collections.
One-to-one mapping: Create a WebSnips collection for each Omnivore label you actively used. Labels you created experimentally and rarely applied can be dropped — the migration is a chance to simplify.
The library-building opportunity: For students and researchers, the Omnivore migration is a good moment to rebuild your research organization more intentionally. Rather than recreating the same label structure, ask: how do I want to organize my research for the next 6-12 months? What topics or projects am I working on? Build collections around those, and import your Omnivore articles into them rather than recreating your old structure.
Omnivore's primary integration was with PKM tools — Obsidian, Logseq, Roam. If you were using Omnivore as the capture layer feeding into Obsidian, WebSnips can serve a similar role.
The key difference: Omnivore had a direct Obsidian plugin that could push highlights and notes directly to Obsidian vaults. WebSnips doesn't have this integration. If the Obsidian pipeline was central to your workflow, consider whether a self-hosted Omnivore/Hoarder alternative or Readwise (which has the Obsidian integration) is a better fit than WebSnips.
| Feature | Omnivore | WebSnips |
|---|---|---|
| Reading mode | Good | Not a reading mode tool |
| Highlight/annotation | Strong (with PKM integrations) | Not applicable |
| Newsletter ingestion | Supported | Not applicable |
| Open-source | Yes | No |
| Self-hosting | Possible | No |
| Obsidian/Logseq integration | Direct plugin | Not applicable |
| Full-page content capture | Article text stored | Full-page capture |
| Organization | Labels | Collections |
| Active hosted service | Shut down | Actively maintained |
Be honest about the trade-offs: Omnivore's PKM integrations (Obsidian plugin, Logseq integration) were a significant feature for its user base. WebSnips doesn't have these integrations. If the Obsidian pipeline was the reason you chose Omnivore, WebSnips may not be the right replacement.
If you used Omnivore primarily as a read-later and research archive without the PKM integrations, WebSnips serves the research organization use case well.
Is there a way to get my Omnivore highlights into WebSnips? Not automatically — WebSnips doesn't have an inline highlight layer, and there's no import path for Omnivore's highlight format. For your most important annotations, copy them manually into WebSnips clip notes.
I want to keep the Obsidian integration. Should I use a different tool? If the Obsidian pipeline is essential, look at Readwise (which has a robust Obsidian plugin) or the self-hosted Hoarder fork of Omnivore. WebSnips doesn't currently have a PKM integration.
Can I self-host Omnivore and keep using it? The community fork Hoarder (gethoarger.app) is an active self-hosted alternative that can import your Omnivore data. If you're comfortable with self-hosting, this may be the most complete migration path.
What about Omnivore's RSS/newsletter features? WebSnips doesn't have RSS or newsletter ingestion. For newsletter reading, consider a dedicated newsletter reader or a read-later app with newsletter support alongside WebSnips for web capture.
Migrating from Omnivore to WebSnips is primarily for users who used Omnivore as a research archive and capture tool rather than for its PKM integrations. The URL export migrates cleanly; the highlights and annotations require manual carry-over for the most important sources.
For students and researchers who want an actively maintained hosted tool for web capture and research organization — without the need for Obsidian or Logseq integration — WebSnips provides a focused alternative.
For more on this, see Best Web Clipper Extensions.
More WebSnips articles that pair well with this topic.
How to migrate from Evernote to WebSnips — a step-by-step guide for knowledge workers who are ready to leave Evernote and want to move their web clips
How to migrate from Instapaper to WebSnips — a practical guide for students and lifelong learners who use Instapaper to save articles for later and want
How to migrate from Matter to WebSnips — a practical guide for writers and content creators who use Matter as a read-later and research tool and want to
How to migrate from Notion to WebSnips — a practical guide for PKM enthusiasts who use Notion as a research and web clipping hub and want to move their
How to migrate from OneNote to WebSnips — a practical guide for knowledge workers who use OneNote as a web clipping and research collection tool and want
How to migrate from Pocket to WebSnips — a practical guide for users who are leaving Pocket after Mozilla shut it down and want to move their saved