Free tool · works now

Export Round-Trip Comparator

Audit conversion fidelity between original notes and exported Markdown to catch missing attachments and dropped metadata.

Runs 100% in your browser. Compare original notes against exported or converted Markdown across headings, wikilinks, image attachments, frontmatter YAML, and callouts to catch silent data loss before migration.

Export Round-Trip Fidelity Workbench

🔒 100% Browser-Local🖼️ Attachment Loss Guard📋 YAML Metadata Audit🛡️ Formula-Guarded CSV

Fidelity Audit Breakdown

Fidelity: 55%
CategoryIdentifierRound-Trip StatusOriginal SourceConverted VariantAudit Details
metadatafrontmatter: titlePRESERVEDSystem Architecture & Deployment RunbookSystem Architecture & Deployment RunbookMetadata key and value preserved identically
metadatafrontmatter: statusPRESERVEDverifiedverifiedMetadata key and value preserved identically
metadatafrontmatter: tierMISSINGproduction—Metadata property dropped in exported file
metadatafrontmatter: tagsPRESERVED[core, infra, security][core, infra, security]Metadata key and value preserved identically
attachmentembed: assets/topology-v2.pngMISSINGassets/topology-v2.png—Attachment was stripped or omitted during round-trip export
headingH1: System ArchitectureCHANGEDH1 System ArchitectureH2 System ArchitectureHeading level shifted from H1 to H2
headingH2: Core ServicesPRESERVEDH2 Core ServicesH2 Core ServicesHeading title and hierarchy level preserved
linklink: Security ControlsMISSINGSecurity Controls—Link destination omitted in export
linklink: Disaster RecoveryPRESERVEDDisaster RecoveryDisaster RecoveryLink target and anchor text preserved
calloutcallout: [!NOTE]MISSINGNOTE—Callout block flattened or stripped
code-blockcode: yamlPRESERVED43 chars43 charsCode block content matches identically
55%Retention Rate
6Preserved Items
4Missing Elements
1Modified Items
1Lost Attachments

The Mechanics of Export Round-Trip Fidelity: Preventing Silent Information Loss

1. The Silent Degradation Hazard in Note Migrations

Migrating digital knowledge bases between applications is one of the most perilous operations in personal knowledge management (PKM) and organizational documentation. Whether moving notes from Notion to Obsidian, exporting Apple Notes into plain text, or converting Markdown documents into static websites, authors face a deceptive phenomenon: superficial visual plausibility masking catastrophic structural loss.

When reviewing exported files, human readers naturally focus on body paragraphs and headings. If the prose appears intact, the export is assumed successful. However, modern note engines rely heavily on non-prose metadata and linked assets: YAML property blocks, embedded diagrams, bidirectional wikilinks, callouts, and preformatted code fences. If an export pipeline silently strips image references or drops frontmatter tags, the underlying knowledge graph is permanently degraded.

2. Why Text Diffing Tools Fail on Document Round-Trips

Standard line-by-line diff utilities (such as GNU diff, git diff, or simple string distance algorithms) are fundamentally inadequate for evaluating conversion fidelity. Standard diffs evaluate character sequences and whitespace formatting. If an exporter re-wraps paragraphs, introduces different blank line spacing, or converts 2-space indents to 4 spaces, line-based diff tools produce hundreds of false-positive warnings.

More critically, line diffs fail to understand semantic equivalence. A wikilink [[Architecture]] converted into a standard Markdown link [Architecture](architecture.md) represents successful link preservation, not a total deletion and insertion. Our Export Round-Trip Comparator bypasses line-level fragility by constructing parallel Abstract Syntax Tree (AST) representations across six functional dimensions:

  • Frontmatter Metadata: Compares YAML key-value dictionaries independently of line ordering or quote formatting.
  • Media & Attachment References: Audits image embeds, diagram assets, and PDF links to verify that zero multimedia files were dropped.
  • Heading Hierarchies: Validates section title continuity while identifying unintended heading level demotions or promotions.
  • Hyperlink Integrity: Checks destination targets and anchor text across both standard web URLs and internal note links.
  • Callout Blocks: Detects whether containerized callout admonitions ([!NOTE], [!WARNING]) survived or were flattened into unstyled prose.
  • Code Blocks: Verifies preformatted code snippet contents and syntax highlighting language specifiers.

3. Six Conversion Fidelity Dimensions Evaluated

Our comparison engine isolates and evaluates six foundational structural tiers:

DimensionWhat is AuditedCommon Failure ModesPreservation Significance
Image Attachments![alt](url) and ![[file.png]]Image tags completely omitted or replaced with broken local pathsCritical: Prevents permanent loss of technical diagrams & figures
YAML FrontmatterDocument title, status, tags, dates, custom keysEntire --- blocks stripped by naive Markdown exportersCritical: Preserves indexing, Dataview queries, and project taxonomy
HeadingsATX level depths (# through ######) and titlesH1 converted to H2; heading anchors brokenHigh: Preserves table of contents structure and reading hierarchy
Wikilinks & Web Links[[Note|Alias]] and [Anchor](URL)Target note names corrupted, slugified, or droppedHigh: Maintains bidirectional graph traversability
Callout Blocks> [!NOTE], > [!TIP], > [!WARNING]Callouts flattened into ordinary blockquotes or lostMedium: Preserves high-urgency warnings and visual emphasis
Code BlocksLanguage specifier, syntax content, indentationIndentation flattened; language tags omittedHigh: Guarantees runnable code examples remain intact

4. Safe Audit Logs and Spreadsheet Security Guarantees

When executing vault-wide migration verification, documentation leads require reproducible audit logs that can be analyzed in spreadsheet applications. When exporting audit logs to CSV, our engine defends against Formula Injection (CSV Injection). If any metadata key, heading title, or URL starts with spreadsheet operator triggers (=, +, -, or @), the field is sanitized with a prepended apostrophe (') and escaped.

Furthermore, this utility operates with zero remote telemetry. No documents, tokens, or comparison results are sent over the network. All comparisons happen locally in browser memory, providing complete compliance with air-gapped data retention mandates.

Frequently Asked Questions

Questions

Why can two documents with identical prose still suffer from severe data loss during export?

Many export tools, word processor importers, and static site generators prioritize visible paragraph text while silently dropping non-prose structural elements. Embedded image attachments, PDF figures, frontmatter YAML metadata properties (such as custom tags or publication dates), and callout formatting boxes are frequently stripped or flattened without warning. To the casual eye, the rendered text looks identical, but critical assets and metadata have vanished.

How does the comparator detect missing image and media attachments?

The engine parses both documents to extract all media embed tokens (both standard Markdown image syntax ![alt](target) and Obsidian wikilink embeds ![[attachment.png]]). It correlates each target reference across both files. If an attachment present in the original document fails to appear in the converted output, it is flagged as missing with high visual prominence.

How are frontmatter YAML metadata differences audited?

The comparator parses YAML frontmatter blocks bounded by triple hyphens (---). It verifies that every custom metadata property (such as status, tier, author, aliases, or date) exists in both files with matching values. Dropped properties are marked as missing, modified values are flagged as changed, and unexpected additions are tracked.

Can the tool identify heading level shifts (such as H1 demoted to H2)?

Yes. When converting documents between Markdown flavors or HTML documentation systems, titles are frequently shifted (for example, converting an H1 document title to H2 to accommodate a website template). The comparator detects near-identical heading titles across documents and flags any hierarchy depth changes.

Does this tool upload my documents to external servers or cloud AI models?

Never. The comparison engine runs 100% in your local browser JavaScript environment. No document text, metadata, or attachment paths leave your device.

Verify Your Notes Across Every Migration

Explore our browser-local tools for vault health inspection, broken wikilink auditing, and Markdown link inventory.

tools export round trip comparator downloadDownload for Mac

No account needed. Intel Mac build