# Use an Existing Markdown Vault

> A good folder workflow begins with a recoverable source. Check a small, representative copy before bringing a valuable vault into a new editor.

Local files, Markdown and AI on your device in one workspace.

Canonical: https://pocketorbitnotes.app/help/use-an-existing-markdown-vault
Language: en-US
Published: not provided
Last updated: 2026-10-18

## Which version does this guide describe?

Follow this guide in your Pocket Orbit workspace. You can also open the sample material in an ordinary Markdown editor.

- [Current availability](https://pocketorbitnotes.app/download)

## 1. Keep a separate backup.

Copy the whole folder, including linked assets and any companion files. Do not treat a synchronised folder as your only backup. Keep the original apart from the test copy.

## 2. Choose representative notes.

Include frontmatter, aliases and tags, headings, links, a block reference, relative attachments and a Unicode filename. Add any important plugin syntax you actually use.

The sample vault is synthetic and intentionally small. It provides examples to inspect; it is not a certificate for your own vault.

## 3. Confirm folder access.

Choose the folder deliberately and check what the app adds during adoption. Existing text and metadata should remain understandable, and any original backup should remain available.

Mac folders, iPad Files providers and iCloud can have different availability and permission behaviour. Check the provider permissions before opening a folder and keep a separate backup.

## 4. Edit and reopen.

Make a small change, reopen the note and inspect it in the other editor. Verify a heading, a link and an attachment. Check that positioned content and original ink remain with their companion.

If two applications edit at once, inspect how conflicts are preserved. Stop if a change is silently overwritten or source files become unavailable.

## 5. Record the exact combination.

Write down app versions, operating system, provider and the note features tested. Mark untested combinations separately.

A successful Markdown round trip does not establish editable ink interoperability or support for all Obsidian plugins. Use the compatibility worksheet to keep those results distinct.

## Run a reversible folder test

Copy a representative folder with a Unicode filename, a relative image, a reference link and a plugin-specific block. Record the untouched originals. Change one heading, reopen externally, and compare only the intended edit. An unsupported embed remains a compatibility finding, not proof the whole vault is supported.

- [Local AI for Your Markdown Vault](https://pocketorbitnotes.app/features/local-vault-ai)
- [Review external edits and conflicts](https://pocketorbitnotes.app/help/external-edits-conflicts)
- [Markdown workspace compatibility checklist](https://pocketorbitnotes.app/resources/compatibility-checklist)
- [How we test file preservation](https://pocketorbitnotes.app/research/preservation-method)

## Related pages

- https://pocketorbitnotes.app/features/local-vault-ai
- https://pocketorbitnotes.app/learn/handwriting-to-markdown
- https://pocketorbitnotes.app/research/native-device-compatibility
- https://pocketorbitnotes.app/help/external-edits-conflicts
- https://pocketorbitnotes.app/resources/compatibility-checklist
- https://pocketorbitnotes.app/research/preservation-method

Source: Pocket Orbit. Please cite the canonical URL.