Inspect the source before moving it
Obsidian documents internal links in both Markdown-link and wikilink forms. A standard link such as [Plan](plan.md) is more portable than [[Plan]] because many non-Obsidian readers do not resolve vault names in the same way. Embedded files and block references add another layer. Obsidian’s callout documentation shows syntax inside blockquotes that some other renderers may leave as text.
Make a small, non-private test vault: one standard link, one wikilink, one embed and one callout. Open the actual files in the destination app and record which behaviors work. Do not infer support for an entire vault from a single README. The portable docs lab gives a standard-link baseline.
Keep a usable fallback
If you must share documentation outside Obsidian, consider adding conventional Markdown links for essential navigation and including assets in the folder. Keep the original vault if you rely on Obsidian-specific features. Obsidian itself supports opening external files in recent versions, so moving to another reader is a choice of workflow, not a missing basic capability.
Aero Markdown can read local Markdown, but this guide does not assert complete Obsidian syntax compatibility. The Mac app is not publicly available yet; test your own vault after release. For a broader choice of apps, see the Markdown workflow comparison.