Free browser tool · zero cloud lock-in

Joplin Export Inspector

Audit Joplin JEX and RAW archives, reconstruct notebook hierarchies, map tags, and diagnose E2EE encryption blocks.

Runs 100% locally in your browser. Audit Joplin JEX and RAW exports before migrating to Markdown or Obsidian. Reconstruct nested notebook hierarchies, map tags and internal resource links, identify To-Do completion states, and diagnose blocked E2EE encrypted notes.

Step 1: Paste Joplin Export Payload

Paste contents from a Joplin JEX file, RAW note file, or multi-item export text dump.

Load Sample Fixtures:

Step 2: Archive Inspection Summary

Overview of parsed items, notebook hierarchy depth, and encryption security status.

3Total Notes2 readable · 1 encrypted
2Notebooks (Folders)Engineering & Architecture, Sprint Planning
1To-Do Notes0 completed · 1 pending
1Blocked Encrypted (E2EE)Action required in Joplin
Joplin Archive Warnings & Security Alerts:
  • CRITICAL: Detected 1 encrypted note(s). Joplin End-to-End Encryption (E2EE) is active. Markdown vaults cannot read encrypted ciphertext. You must decrypt these notes in Joplin prior to exporting.

Step 3: Notes & Notebooks Inventory Ledger

Audited note attributes, reconstructed folder hierarchy paths, and encryption readiness.

TitleNotebook PathType / StatusTagsLinksEncryption Diagnosis
Architecture Design DocumentEngineering & ArchitectureNote#Backend2 internal · 1 mediaReadable
Sprint 12 Implementation TasksEngineering & Architecture / Sprint PlanningTo-Do (Pending)—0 internal · 0 mediaReadable
Encrypted Financial RecordsEngineering & ArchitectureNote—0 internal · 0 mediaBLOCKED (E2EE)

Step 4: Converted Markdown Preview

Obsidian-ready Markdown representation with reconstructed folder frontmatter and wikilinks.

Clean Markdown Outputnote-1.md
---
title: "Architecture Design Document"
notebook: "Engineering & Architecture"
date_created: 2024-05-10T12:00:00.000Z
date_modified: 2024-05-11T14:30:00.000Z
tags:
  - joplin/backend
---

Architecture Design Document

# Architecture Design Document

Reviewing distributed local-first storage design.
See referenced diagram: [[Architecture Diagram]]
Also see [[Sprint 12 Roadmap]]

Understanding Joplin Export Architecture and E2EE Migration Mechanics

Joplin is a popular open-source note-taking application designed for synchronized personal knowledge management across desktop and mobile operating systems. When planning a migration from Joplin to file-based, local-first environments such as Obsidian, Logseq, or Git-backed Markdown vaults, understanding how Joplin organizes and exports notes is crucial for preserving your structure, attachments, and links without data loss.

1. The JEX and RAW Storage Formats

Unlike plain Markdown folders, Joplin stores your active notebook inside a local SQLite database (database.sqlite). When you choose File > Export All > JEX - Joplin Export File, Joplin packages your database into a single uncompressed tar archive. If you select RAW - Joplin Export Directory, Joplin dumps those exact files into a standard filesystem directory.

Inside both JEX archives and RAW folders, every database entity is represented as an individual .md file named after its 32-character hexadecimal UUID (for example, aaaaaaaaabbbbbbbbbcccccccccddddd.md). The file begins with the item title or Markdown body, followed by two blank lines, and terminates with a metadata key-value header block ending with the type_: <number> property:

  • type_: 1: Standard notes and To-Do items.
  • type_: 2: Notebook folders.
  • type_: 4: Resource metadata files (images, PDFs, audio).
  • type_: 5: Tag definitions.
  • type_: 6: Note-to-tag junction links.

Because folders and tags are serialized as relational records rather than physical filesystem directories, simple scripts that copy .md files directly will leave you with an unorganized collection of 32-character UUID filenames without folder structures or tags. This inspector parses the relational links to reconstruct the complete folder hierarchy.

2. The E2EE Encryption Block: Why Encrypted Notes Cannot Be Migrated Directly

Joplin features robust End-to-End Encryption (E2EE). When E2EE is enabled, notes, notebooks, and attachments are encrypted client-side using AES-256 before synchronization with Nextcloud, Dropbox, Joplin Cloud, or WebDAV servers.

A critical limitation of Joplin export functionality is that if you export while synchronization is paused or if notes are exported in their synchronized state, the exported text files will contain raw AES ciphertext starting with headers such as JOPLIN_CIPHER_V1: and encryption_applied: 1.

No Markdown viewer or Obsidian importer can read or decrypt this ciphertext. Attempting to import encrypted JEX files results in permanently unreadable gibberish. This tool enforces a strict rule: encrypted notes are never declared readable. If encrypted notes are detected, the tool alerts you that you must open the Joplin desktop client, ensure E2EE decryption is 100% complete across all local notebooks, and re-export the archive with encryption disabled before continuing.

3. Resolving Internal Joplin Links (:/id) to Wikilinks

In Joplin, internal links between notes and media references use an internal URI scheme: [Link Text](:/32hexUUID). For example, linking to an image stored in Joplin produces ![diagram.png](:/11112222333344445555666677778888).

In Obsidian and CommonMark, these internal URIs result in broken links because there is no server resolving the UUID. During migration, these URIs must be mapped:

  • Resource references must be mapped to the actual resource filename located in the resources/ folder and converted to transclusion syntax (![[diagram.png]]).
  • Note-to-note references must be resolved by matching the destination UUID to its corresponding note title, converting the URI into a standard wikilink ([[Target Note Title]]).

4. Reconstructing Notebook Folder Trees from Relational Links

In Joplin, notebooks can be nested arbitrarily deep (e.g., Work > Clients > Acme Corp > Q3 Deliverables). However, Joplin does not save this hierarchy as nested filesystem paths. Instead, each notebook item contains a parent_id field referencing its parent notebook.

This inspector traverses the parent ID chain starting from the root notebooks (where parent_id: "") down to child notebooks, constructing the full breadcrumb path for every note. When converting notes to Markdown, this path is written into YAML frontmatter (notebook: "Work / Clients / Acme Corp") so automated vault organizational tools or folder plugins can place the note in its appropriate folder.

5. To-Do Items and Synchronization Conflicts

Joplin combines standard prose notes and To-Do checklists in the same library. A note is designated as a To-Do if its header contains is_todo: 1. If completed, todo_completed contains the Unix epoch timestamp in milliseconds when the item was checked off. This tool inventories completed versus active To-Dos, allowing you to distinguish task management records from permanent reference notes.

Furthermore, if concurrent edits occurred across multiple devices during synchronization, Joplin generates conflict notes marked with is_conflict: 1. This tool flags conflict notes so you can review and resolve diverging edits prior to importing them into your permanent vault.

6. Security and Zero-Cloud Local-First Privacy

Your personal Joplin notebook contains confidential research, personal records, and credentials. In strict accordance with our local-first privacy commitments, this tool executes 100% in local browser memory. It loads no external tracking scripts, executes zero network API calls, and never transmits your note bodies, metadata, or encryption keys to any remote cloud endpoint.

Frequently Asked Questions

Common technical questions regarding Joplin JEX exports and Markdown vault migration.

Questions

What is the difference between Joplin JEX and RAW export formats?

A Joplin JEX (Joplin Export) file is an uncompressed tar archive containing markdown files and a resources directory. A RAW export is an uncompressed filesystem folder containing the exact same files. In both formats, each note, notebook, tag, and resource metadata entry is serialized as a plain text file ending with Joplin metadata headers.

Can markdown importers or Obsidian open E2EE encrypted Joplin notes?

No. When Joplin End-to-End Encryption (E2EE) is turned on, note bodies and resource files are encrypted with your master key using AES-256 before synchronization. If you export without decrypting, the notes contain ciphertext blocks starting with JOPLIN_CIPHER. You must ensure all notes are fully decrypted in the Joplin desktop client before exporting.

How does Joplin store folder hierarchies and tags?

Joplin uses relational metadata rather than nested filesystem folders. Notebooks are items with type_: 2 and parent_id links. Tags are items with type_: 5, connected to notes via note_tag junction records (type_: 6). This tool parses these relational links and reconstructs the full folder path and tag list for each note.

What are Joplin internal links (:/32-hex-id)?

When you link to another note or insert an image in Joplin, Joplin writes internal markdown links using a colon-slash prefix followed by a 32-character hexadecimal ID (e.g., [Note Title](:/1234567890abcdef1234567890abcdef)). Standard markdown renderers cannot resolve these IDs. This inspector inventories these links and converts them to Obsidian wikilinks and embedded transclusions.

How are Joplin To-Do items preserved when migrating to Markdown?

Joplin differentiates standard notes from To-Do items using the is_todo: 1 header. Completed tasks have todo_completed set to a timestamp. When converting to CommonMark, To-Dos can be assigned frontmatter flags and formatted with GitHub Flavored Markdown task list syntax (- [ ] and - [x]).

Does this tool transmit my Joplin notes or encryption keys over the internet?

No. This utility executes 100% in local browser memory. No text, metadata, attachment filenames, or encryption headers are sent to remote servers or cloud endpoints.

Keep your notes private, portable, and fast

Write your daily records in clean, future-proof plain Markdown on your local disk with zero cloud lock-in.

joplin export inspector downloadDownload for Mac

No account needed. Intel Mac build