Appearance
Import & export
Import
Go to Settings → Data & sync → Import. Drop files on the import area or click it to choose files. To pick a whole folder, such as an unzipped Obsidian vault, click Choose a folder instead.
From Markdown
Drop one or more .md or .txt files. Each file becomes a new page, and Markdown formatting such as headings, lists, to-dos, code, quotes, bold, italic, and links becomes native blocks.
From Notion
- In Notion, export your content as Markdown & CSV, with subpages included.
- Drop the exported
.zipfile into Aurora's import area as it is. - Aurora imports pages, databases and their rows, the links between databases, and attachments.
When the import finishes, Aurora lists anything it could not bring across exactly, for example a date range that kept only its start date, or an attachment that was missing from the export.
From Obsidian
Zip your vault folder and drop the .zip file, or choose the vault folder directly. Folders, [[wikilinks]], properties, tags, attachments, Bases, and canvases come across. Dataview queries are kept as code blocks so nothing is rewritten silently.
Let AI check property types
For Notion and Obsidian imports, turn on Let AI review the types it guessed to have AI check the property types the importer chose. It uses your own provider key, or AuroraAI for Notion imports. Aurora sends only column and property names, their distinct values, and counts, never your page text.
Export
Single page — Markdown
- Open the page.
- Click ··· (page menu) → Export as Markdown.
- A
.mdfile downloads to your device.
Single page — JSON
- Open the page.
- Click ··· (page menu) → Export as JSON.
- A
.jsonfile downloads containing the raw block structure.
Single page — HTML
- Open the page.
- Click ··· (page menu) → Export as HTML.
Single page — Print or PDF
- Open the page.
- Click ··· (page menu) → Print / Save as PDF.
- Aurora opens a print-safe snapshot of the page and triggers the browser print dialog. Use your system dialog to print or save as PDF.
Readable exports and E2EE
Markdown, HTML, and print/PDF exports are readable plaintext. If the workspace is encrypted, Aurora blocks readable export until the workspace is unlocked and warns before creating files outside Aurora's encryption boundary.
Inline databases, linked databases, inline task blocks, and inline collections export as best-effort static snapshots. Some Aurora-native structures may still be represented as fallbacks rather than full-fidelity editable content.
Full workspace — Markdown or HTML
- Go to Settings → Workspace → Export. Only workspace owners can export.
- Click Download ZIP for every page as a Markdown file with its properties at the top, or Download as HTML for a self-contained website you can read offline.
TIP
The Markdown ZIP is a good way to move to another tool, since the files are plain text you can open in any editor. For a full backup you can restore into Aurora, use AuroraBak instead.
AuroraBak backups
AuroraBak files (.aurorabak and .aurorabak-bundle) are Aurora's native backup and restore format. They preserve the workspace structure, page data, workspace settings, and bundled media needed for an Aurora restore. Create and restore them in Settings → Data & sync → Backup; see Version history & backups.
In a backup of an encrypted workspace, page content stays encrypted, but images and attachments are saved unencrypted; a password-protected backup encrypts the whole file. Restore requires the same recovery method that normally unlocks the workspace — a trusted device, your recovery phrase, or a key file. (E2EE unlock is independent of your login password; see Security & encryption.)
Encrypted AuroraBak files can be restored into their original workspace identity. Creating a new workspace from an encrypted AuroraBak is blocked until Aurora can re-wrap the encrypted workspace key for that new workspace.
Use Markdown or HTML export when you intentionally want a readable plaintext copy of an unlocked encrypted workspace.
Clean Markdown local folders
Clean Markdown is a Local folders mode, not the same thing as one-time export. Keep mirrored writes readable Markdown out of Aurora; Clean sync also imports supported Markdown body edits back into Aurora for enrolled workspaces.
See Sync & storage.
File attachments
Files attached to pages are stored in the active workspace storage path: local folder storage for folder-backed workspaces, AuroraCloud page storage for cloud workspaces, and encrypted storage when E2EE covers the file path. They are included when the export path supports them.
Download individual attachments by clicking the file block in the editor.
