Moved the file.
Lost the pictures?

The image may not be inside the Markdown file.

A common Markdown image reference points to a separate file. If you are adding a new picture, start with the screenshot and image insertion guide. The path is often relative to the folder containing the .md document.

Project/
├── Notes.md
└── Notes-assets/
    └── chart.png

In Notes.md:
![Project chart](Notes-assets/chart.png)

If you move only Notes.md into another folder, that relative location no longer contains the picture. The source text can be intact even though the rendered image disappears.

Put the path and the actual file back together.

1. Move the document and its image folder together.If you still have the original assets, put the .md and its companion folder in the same relationship as before. Keep the folder name used in the image link.
2. Correct the path in Source.Switch to Source (⌘2), or Split (⌘3) to keep Preview visible. Update the image reference to match the picture’s actual location.
3. Choose a replacement in Zizeg.A missing or unreadable local image appears as a broken-image placeholder. Click it and choose the correct image file; Zizeg updates the reference.

Use the option that matches what happened. You don’t need to reorganize a shared image collection just to repair one document.

The file can be present but unreadable.

If the image exists at the expected path, check whether Zizeg has access to its folder. macOS may ask you to approve the document’s containing folder so the app can work with sibling assets.

Also check that a cloud-stored image is actually available on the Mac. A correct path cannot display a picture that has not downloaded or is no longer accessible.

A web image is a different case. If the reference starts with https:// or http://, moving the .md may not be the cause. Check the URL, connection, and the app’s remote-content policy rather than looking for a sibling image file.

If the source is an online URL, follow the remote-image troubleshooting guide to distinguish approval from URL or server problems.

Rename the document without losing its assets.

When you rename a document in Zizeg using the filename control in the window title bar, an assets folder that belongs to the document is renamed too, and its relative image references are updated.

After a Finder rename, Zizeg can offer to rename the owned assets folder and update the links when they no longer match. External or shared folders are not changed automatically.

Moving to a different directory still requires preserving or updating the file relationships. Rename handling is not a promise that every arbitrary move repairs every image automatically.

Use Save As when creating another version.

Choose File → Save As… (⇧⌘S) and choose the new location. The panel lets you use Assets Folder or Base64 Data URI image storage. Zizeg can copy or convert accessible images and adjust the new document’s references while leaving the original unchanged.

Assets keep images as separate files; Base64 embeds them into a larger Markdown source file. For a simple editable handoff, keeping the document and its asset folder together is often the easiest structure to understand.

For a worked size comparison and the Save As conversion steps, see Markdown images: separate files or Base64 embedding?

Send a packaged reading copy instead.

If your recipient doesn’t need the source, you can avoid the Markdown-and-assets handoff. Standalone HTML embeds accessible local and approved remote images into a browser-readable file. PDF gives them a fixed-page document.

Fix missing pictures before exporting, then open the exported copy and check it. Export cannot reconstruct an image that is no longer available.

For the broader choice, see which format to send.