The same file.
A different-looking document.

First ask what actually changed.

A heading with a different font is still a heading. A diagram that never renders is a different issue. Inspect Source before assuming the file was corrupted, then choose the fix for the actual cause.

Use the same source in both apps.

This example includes a heading, a line break inside a paragraph, a pipe table, an escaped pipe inside a cell, and a Mermaid code block.

# Project update

First line
second line in the same paragraph.

| Task | Status |
| --- | --- |
| Review | Ready |
| Label A \| B | Checked |

```mermaid
graph LR
  Draft --> Review
```

Download the specimen and open the same copy in each app. Compare the structure as well as the appearance. This is an inspection exercise, not a claim that the two apps will produce identical output.

A new source line is not always a new paragraph.

The specimen’s two lines of prose belong to one paragraph because there is no blank line between them. A soft line break can be rendered as a space or a line break; a narrow window may also wrap a line without changing the source.

When you want a new paragraph, separate it with a blank line. If you need a deliberate line break inside the paragraph, check the syntax supported by your destination. The CommonMark soft-break rules and hard-break rules describe the distinction.

Check the feature, not just the .md extension.

Pipe tables are an extension described in the GitHub Flavored Markdown specification. They need a header and delimiter row. In a cell, \| represents a literal pipe instead of a column separator, as in the “Label A | B” example.

If a table stays as source text, check whether the receiving app supports pipe tables and whether the delimiter row is present. If columns split unexpectedly, inspect literal pipes in cell content. For editing an existing table in Zizeg, see the visual table guide.

The Mermaid block illustrates a separate extension. An app with diagram support may render it as a diagram; an app without that support can show a fenced code block instead. Zizeg supports common Markdown features and core GFM features such as tables, task lists, and strikethrough; it does not render Mermaid diagrams, math, or footnotes.

Front matter and raw HTML also receive app-specific treatment. Zizeg presents front matter separately in Preview and applies safety and support rules to raw HTML, so an HTML-heavy document may look different from a browser page.

Look at what the file contains.

Open the .md in Zizeg. If it is your default Markdown app, double-click the file in Finder. Choose Split (⌘3) to compare the source with its formatted view; if Split is your default viewing mode, both panes are already there. Click the active Split control again to swap their order.

Check the heading markers, paragraph boundaries, table delimiter row, and fenced code. Reading the file is free. If you need to change the source, editing is available through a one-time unlock or an active subscription.

If pictures are missing, diagnose them separately: local paths and folder access or remote URLs and loading controls.

Match the document to its destination.

• Use headings, paragraphs, lists, links, and fenced code for a straightforward shared document.
• Check that the receiving app supports any tables or specialized syntax you rely on.
• Keep image assets with the source, and check their paths.
• Open a sample in the destination app before committing to a workflow.

If consistent presentation matters more than further editing, send a checked PDF or standalone HTML copy. The format-choice guide compares those handoffs.

If the saved source itself has changed, follow the focused-edit and source-review guide rather than changing display settings.