Back to blog
6 min readJune 6

Omnivore alternatives in 2026: where to move after the shutdown

Omnivore is gone. This covers getting your data out, what to check on import, and where to move if you want recall rather than another reading queue.

Omnivore alternatives in 2026: where to move after the shutdown

Omnivore alternatives in 2026: where to move your saved articles and highlights

Omnivore shut down its hosted service on November 15, 2024, and hosted user data was deleted. The best replacements are Readwise Reader or Raindrop for read-later, or an ask-your-saves tool like dEssence if you want to recall what you saved, not just store it. Pick based on whether you want reading or recall.

The Omnivore code is still on GitHub under an open-source license, so self-hosting is technically possible. For most people that is not a real option. Running and maintaining your own server is a project, not a migration, and it comes with updates, backups, and downtime to babysit. So the practical question for almost everyone is which hosted tool to move to, and what to honestly expect from it.

It is worth slowing down on this choice. The shutdown was a reminder that a saved-article library is only as safe as the company hosting it. Picking the next tool on price alone is how people end up migrating twice.

First, get your data out

If you exported your Omnivore library before the shutdown, you have a file of your saved articles and highlights. If you did not, the hosted data is gone and there is no retrieving it, which is the hard lesson of relying on a single free service with no backup of your own. The code being open source does not help here, because the code never contained your personal saves. Going forward, favor tools that let you export easily, so you are never trapped the same way again.

Before you pick a destination, look closely at what it accepts on import. Some tools take a list of URLs and re-fetch the articles. Some take highlights as a separate file and attach them to the right pieces. Some take neither and quietly expect you to start fresh. A few promise import but choke on a large file. Knowing this before you commit saves a frustrating afternoon and a second migration.

What to look for in an Omnivore replacement

Omnivore was a read-later app with highlighting and a clean reader. If you want a like-for-like swap, look for that same shape: a reading queue, highlight support, and reliable sync across your devices. Instapaper covers the basic read-later job and has been stable for years. Several newer apps aim at former Omnivore users specifically, so compare their import paths before you commit.

If the shutdown made you rethink the whole habit, raise the bar instead of just replacing the queue. The real value of a saved-article pile is being able to find and use it later, not the saving itself. So look for search by meaning rather than keyword, the ability to ask in your own words and get an answer from your saves with sources, and low filing overhead so you are not re-tagging everything you import. If a tool makes you organize on the way in, it will go stale the same way a vault does.

The honest reframe many former Omnivore users land on is this: the reading queue was never the point. The point was remembering what they read. If that is true for you, a recall tool fits the need better than another reader.

One more thing worth checking is how much each tool asks of you after import. A read-later app that expects you to re-foldering and re-tag a few hundred imported articles is handing you a weekend of admin before the tool does anything for you. The same articles in a recall tool sit there until you ask about them, which means the migration is finished the moment the import completes. For a library you built over years and rarely revisit, that difference decides whether you actually keep using the new tool or let it become the next graveyard.

Where dEssence fits, and where it does not

dEssence is built for recall rather than reading. You save articles, links, PDFs, videos, screenshots, and voice notes from the browser, Telegram, or the web app, then ask a plain-language question and get an answer drawn from your own saves, with sources. There are no folders, no tags, no organizing. The model is memory you do not have to maintain: save it, forget it, ask for it later.

For a former Omnivore user, the honest caveat is that dEssence is not a direct clone. It does not offer a polished reading view to replace Omnivore's, and it is not primarily a place to sit and read long-form. If what you miss most is the reader itself, the typography, the offline mode, the distraction-free page, a dedicated read-later app will feel more familiar and you should look there first.

Where it earns a look is the part Omnivore never fully solved: actually finding and using what you saved. Omnivore could store and highlight an article, but recalling it months later still meant scrolling or guessing at search terms. If you saved hundreds of pieces and read a fraction, the value was always trapped behind your own memory of what was in there. A tool you can ask in plain words turns that pile from a backlog into something you can query, which is a different relationship with your own archive than a reading queue offers.

Honest about dEssence

Weigh the gaps before you move. dEssence is in beta, so it is less settled than an established app, and migrating into a beta product carries the same kind of risk that bit Omnivore users in the first place: early tools can change direction or pricing. There is no native iOS or Android app yet, so mobile is Telegram and the web rather than a dedicated app, and there is no offline reading mode. Capture is limited to the browser extension, the Telegram bot, and the web app, so importing a large Omnivore highlight export may not be a clean one-click process and could mean re-saving the items you care most about. The free tier has an archive cap, paid pricing is not finalized, and there is no team workspace. If you want a battle-tested reader you can trust to still be around in three years, weigh that maturity honestly against a beta tool.

None of that is a reason to avoid it, only a reason to go in with eyes open and to keep your own export of whatever you save, wherever you land.

Frequently asked questions

Q: Can I still get my data out of Omnivore? No, if you did not export before November 15, 2024. The hosted service is offline and the data was deleted. The open-source code remains on GitHub, but it does not contain your personal saves, so it cannot recover them.

Q: What is the closest read-later replacement for Omnivore? For a like-for-like reading queue with highlights, Instapaper is the simplest established option, and several apps now court former Omnivore users directly. Compare what each accepts on import before you pick, since a smooth migration matters more than a feature list.

Q: Should I self-host the open-source Omnivore code? Only if running a server is something you actively want to do. For most people the upkeep outweighs the benefit, and a hosted tool is the practical move.

Q: How do I avoid losing everything again? Pick tools that make export easy and do not lock your data in. Re-saving the items you truly care about, rather than dumping a giant archive you never revisit, also keeps your library small enough to stay worth searching.

If you want a familiar reading queue, a dedicated read-later app is the closer match. If the shutdown made you want to actually use what you save, a recall tool fits better. dEssence is free during beta with no card, though it is early, mobile is web and Telegram only, and a big highlight import may not be clean.