Skip to content

Export

Orimora lets you take content out of the platform for backups, migration, printing, or offline use.

Open a document. Click the ⋯ menu (or export actions) in the document meta bar:

Format What you get
Export Markdown .md file — title, front matter, body as Markdown
Export Markdown + images (ZIP) Markdown plus embedded image files
Export JSON TipTap/ProseMirror JSON — for advanced integrations
Print / Save as PDF Browser print dialog — use “Save as PDF” as destination

From the sidebar, open a collection menu (⋯ on the collection row):

Option Contents
Export as Markdown (ZIP) All documents in the collection as .md files
Export as HTML (ZIP) Rendered HTML pages

Large collections may take a few seconds — wait for the download to start.

Every member can download a copy of their own data — a GDPR Article 15/20 “right of access / data portability” self-service. Go to Settings → Account → Export my data and download the ZIP. It contains:

Item Contents
profile.json Your account profile (name, email, role, timestamps, SSO externalId)
documents/ The documents you authored (Markdown + JSON)
comments.json The comments you authored
audit.json The audit events where you were the actor
files/ The files you uploaded
web_push_subscriptions.json Your browser push subscriptions (endpoint metadata, no keys)
mfa.json Your MFA status — TOTP enrolment + backup-code counts (no secrets)
passkeys.json Your registered passkeys (labels, timestamps — no credential secrets)
notifications.json Your in-app notifications

A team admin can export the entire team’s content as one ZIP from Settings → Team → Export team data. This is gated by the settings.backup capability (Admins only) and respects per-collection permissions — a collection the admin cannot read is skipped and the skipped count is reported. Use it for a one-off migration or an offline archive; for scheduled, verifiable backups use Backup & Restore instead.

For scripts and the Obsidian plugin:

GET /api/v1/documents?format=markdown
Authorization: Bearer kb_your_key

Incremental sync with updatedSince (ISO 8601) returns only changed documents. See REST API overview.

For ongoing sync to external systems rather than manual export, use one of the outbound options: a Git mirror (push a folder to a repo), a Pull-API folder share (let a static site pull a folder), or Send to (push a single document to a webhook/n8n endpoint).

You need read access to the document or collection. Export respects collection and tag permissions — you cannot export content you cannot view.