Why Evernote's ENEX Export Fails on Large Notebooks (and What to Use Instead)

You export your Evernote notebook, the progress bar completes, everything looks fine — until you count the notes. 600 out of 1,000. No error, no log, no hint about which 400 vanished.

If this happened to you, you’re not alone. Complaints about ENEX exports have been piling up on Evernote’s forums for years. The failures aren’t random; they’re structural. Here are the three reasons, and the workaround that actually holds up.

Reason 1: Everything goes into one giant file

ENEX packs an entire notebook into a single XML file — including every image, PDF, and audio recording, Base64-encoded inline. A notebook with a few gigabytes of attachments becomes a single multi-gigabyte XML document.

At that size, things get fragile: the export can stall, the app can run out of memory, and any downstream tool that tries to parse the file has to load a monster. One corrupted byte and some parsers give up on the whole file.

Reason 2: Silent failures

The worst failure mode isn’t the crash — it’s the export that pretends to succeed. The app says “done,” but the file contains fewer notes than your notebook. No error message. Nothing tells you which notes were dropped.

This is why the single most important migration habit is boring: write down your note count before exporting (it’s in Evernote’s sidebar), then count what came out. If the numbers differ, you caught a silent failure that would otherwise surface months later as “wait, where’s that note?”

Reason 3: The 100-note ceiling

Depending on your client version, you can only select up to 100 notes per export. 2,000 notes means 20 manual rounds — each of which can independently hit reasons 1 and 2. For big accounts, ENEX export isn’t just unreliable; it’s practically unusable.

The workaround: HTML export

Sitting next to ENEX in the export menu is “Export as HTML,” and it behaves completely differently:

• One folder per note instead of one giant file — no size ceiling to hit
• Attachments saved as real files next to each note’s HTML
• Formatting (tables, checklists, images) preserved as ordinary HTML
• Reliable at scale — I exported 3,000+ notes without a single loss

The trade-off: HTML is a great escape format but a poor destination. You get an archive you can read, not notes you can edit or search from your phone.

What to do with the HTML

Two reasonable paths:

Archive path — upload the HTML folders to cloud storage as-is. Fine if you rarely revisit old notes.

Living-notes path — convert them into editable documents. I moved mine into Google Drive as real Google Docs, with notebook structure preserved as folders. Doing it by hand takes about a minute per note; I had 1,640 notes, so I built a macOS app that automates the whole pipeline — HTML parsing, Google Docs conversion, attachments, resume-on-interruption. The free tier does 20 notes if you want to verify the output with your own data: Evernote Migration Tool.

The 30-second summary

1. Don’t trust ENEX for anything over ~100 notes
2. Count notes before export, count again after
3. Use HTML export — it’s the reliable one
4. Decide: archive (upload as-is) or living notes (convert to Google Docs)

Your notes survived years of accumulation. Don’t lose them in the last mile.