Export

QARK exports conversations, groups, and individual messages in three formats. All exports are generated locally — no cloud service or conversion API involved.

Three formats

Format	Output	Assets	Interactive
Markdown (.md)	Plain text with formatting	Linked in _assets/ folder	No
HTML (.html)	Self-contained styled page with embedded CSS	Linked in _assets/ folder	Yes — sibling browser for navigating regenerations
PDF (.pdf)	Print-ready document via headless browser	Embedded via file:// URLs	No

Where to export

Level	Access points
Conversation	Context menu on conversation in sidebar, command palette (Cmd+K → “export”), Info Panel → Export section
Group	Context menu on group in sidebar, command palette → “export group”
Individual message	Export icon (download) in the message action bar — hover over any message to see it

What each format includes

Markdown

• Conversation title, model, creation date, export date
• All messages with role labels (User / Assistant)
• All branches and regenerations — each version labeled as (version X/Y — selected) for the active branch
• Tool call results in blockquote format
• Citations as numbered lists
• Prefetched URLs as blockquote links
• Generated images and videos linked to asset folder
• Thinking blocks are excluded

HTML

Everything in Markdown, plus:

• Embedded CSS (self-contained, no external stylesheets)
• Inline QARK logo as SVG
• Interactive sibling browser — previous/next navigation to browse regenerated versions of any message, with inline JavaScript
• Syntax-highlighted code blocks (dark theme)
• Styled tool call blocks, citation boxes, and thinking blocks (collapsible <details> elements)
• Embedded <video> elements for generated videos

PDF

Same visual output as HTML, with differences:

• A4 page size, 20mm margins
• Page break rules keep messages together
• Sibling browser is non-interactive (flat layout showing all versions)
• Videos replaced with placeholder text ([Video: filename])
• Generated via headless Chromium-based browser (Chrome, Arc, Brave, Edge — auto-detected per platform)

Conversation export

Exports the full conversation thread including all branches. Every regeneration is included — not just the active branch.

File naming: {sanitized_title}.{ext} — special characters (/\?%*:|"<>) replaced with dashes, whitespace normalized.

Asset folder: {title}_assets/ created alongside the export file. Contains:

• Image attachments from messages
• Generated images from image generation tool calls
• Generated videos (Markdown and HTML only — excluded from PDF)

Group export

Exports all conversations in a group as a single file.

Includes:

• Table of contents with conversation list and message counts
• Group metadata (name, export date, total conversations, total messages)
• Each conversation as its own section with title, model, date, message count
• Fork relationships shown with “Forked from:” banners
• All branches and regenerations from every conversation

Sorting: Non-forked conversations first (by creation date), forked conversations after.

Asset folder: Single {group_name}_assets/ folder consolidating assets from all conversations in the group.

Message export

Exports a single message (any role) as a standalone file.

Includes: Role label, timestamp, content, attachments, tool calls, citations, prefetched URLs. No sibling/branch content — just that one message.

File naming: message-{role}-{YYYY-MM-DD}.{ext}

Asset folder: message_assets/

PDF generation details

PDF export uses a headless Chromium-based browser detected automatically:

Platform	Detection order
macOS	Google Chrome → Arc → Chromium → Brave → Edge
Linux	google-chrome → google-chrome-stable → chromium-browser → chromium → brave-browser → microsoft-edge
Windows	Chrome → Edge → Brave (checks Program Files paths)

The HTML is written to a temporary file, rendered headless with --print-to-pdf, and the temp file is cleaned up. If the browser is not found or rendering fails, QARK reports the error — you can fall back to HTML export.