Export

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

Single document export

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

Tip

PDF export uses your browser’s print engine. For batch or automated export, use the REST API with format=markdown or a publishing channel.

Collection export

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.

Personal data export (GDPR)

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

Note

The export is scoped to your own content only — it never includes a teammate’s documents, comments, or files, so one member cannot exfiltrate another’s data through it. Each download is rate-limited to once per 24 hours per user and is itself recorded as an account.export_downloaded audit event.

Full team export (admins)

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.

API export

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.

Publishing channels

For ongoing sync to external systems (webhook, Git mirror, pull endpoint), configure Settings → Publishing instead of manual export. See Publishing channels.

Permissions

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

See also

• REST API overview — programmatic access
• Publishing channels — automated outbound sync
• Obsidian Plugin — selective pull into vaults