What changed between Markdown and HTML?
On 3 October we imported the same fixture into two fresh profiles with synchronization disabled. One used Markdown import mode and the other used HTML. We then exported both using Joplin’s front-matter export command and inspected the files. HTML-mode notes remained HTML files with front matter; their desktop appearance was not evaluated.
| Check | Markdown import | HTML import |
|---|---|---|
| Exported notes | 3 Markdown files | 3 HTML files |
| Red colour and 20px font-size declarations | Absent; words retained | Both declarations retained |
| PNG attachment | Identical bytes | Identical bytes |
| One unambiguous internal link | Points to the exported Markdown note | Points to the exported HTML note |
| Dates and migration tag | Present in all three notes | Present in all three notes |
If presentation carries information in your archive, try the HTML route on a copy before accepting a Markdown conversion. The result here is retention of particular markup in particular files. It does not prove that every complex layout looks identical or that HTML is the better editing format for your work.
Download both actual export sets and the original fixture or inspect the new checks and file hashes.
The original import and restore result
All three synthetic notes arrived in one notebook with four tags, six note-to-tag assignments and one PNG attachment. The exported image was byte-for-byte identical to the input. A link between two notes became a relative link to the correct exported Markdown file.
The input was an ENEX file we generated for this test. It was not exported from an Evernote account. This tests Joplin’s handling of that small format fixture, not every part of an Evernote migration.
What the 23 September trial checked
- Preserved: three titles, created and updated times, bold and italic text, nested bullets, checked and unchecked tasks and four tags.
- Links: one external URL survived. One internal note link was resolved by matching its target title.
- Attachment: the PNG’s hash matched the input after import and Markdown export.
- Lost in Markdown: red text colour and a 20-pixel font-size declaration.
- Archive round trip: importing Joplin’s JEX export into a second fresh profile then exporting again produced identical three Markdown files and PNG bytes.

A small repair checklist
If colour carries meaning in your notes, replace it with explicit text labels before relying on Markdown. Check internal links after export, especially when notes share a title. Keep the original ENEX archive and test a representative notebook with attachments before moving a larger collection.
Inspect the original evidence
- Download the synthetic ENEX input
- Download the actual Markdown export and attachment
- Inspect the counts, file hashes and result record
Method and limits
In the original trial, a research agent used Joplin Terminal 3.7.1 with two isolated empty profiles on Windows and Node 24.1.0. No account, cloud sync or personal notebook was used. Import, Markdown export, JEX export and JEX re-import completed. The output files were inspected independently.
The 3 October extension used the same application version and input with two new isolated profiles. Both imports and exports completed. File-content checks confirmed the table above. No Obsidian trial or visual comparison of desktop editors was performed.
Joplin’s official Windows installation instructions use WSL. This test used native Windows shell mode, so it does not establish a supported Windows installation or test the desktop interface. It is not a performance benchmark or a guarantee of lossless migration.
OCR, encrypted notes, notebook stacks, reminders, duplicate titles, large attachments and complete account export were not tested. The observed internal-link result covers one unambiguous target only.
See Joplin’s official import and export guide and terminal documentation for the supported workflows.
Read Evernote vs Joplin or see Joplin’s sourced profile.
After choosing an import route, use the Joplin sync options guide to separate local notes, storage services and a Cloud subscription.