A Markdown note can point to an image, PDF, or other file. The note’s text and the attachment are usually separate things, so a portable collection must account for both.
Images are references
The common image form looks like this:
The alt text describes the image. The path says where to find it relative to the note. If you move the note without the images folder, the text survives but the image may not appear.
Some apps store attachments inside a package or database and create Markdown references only during export. Others keep ordinary files beside the note. These are different storage models, even if the editor shows the same image while you write.
Choose a layout you can understand
For a small collection, an attachments or images folder near the notes may be enough. For larger collections, a folder per project can make moves safer. Prefer relative paths when you want to copy a folder as a unit. Filenames should be descriptive and avoid depending on a temporary device path.
projects/
garden/
plan.md
images/
garden-sketch.png
Linked PDFs and audio files have the same basic issue: the Markdown text may contain a link, but the linked file needs to move with it. A destination app might not know how to render the attachment inline; a working link is still valuable.
Test before you trust an export
Export one note with an image and one with another file type. Open the .md file in a different editor and follow both links. Then copy the folder elsewhere and repeat. If the links break, inspect the exported paths and the app’s attachment options.
The file guide explains relative links. The export checklist covers a larger collection.