Filename template syntax

Quendian uses a template string to generate export filenames. The template is configured in Preferences → Export → Filename Template.

Default template

YYYY-MM-DD HH-mm {{title}}

This produces filenames like 2024-03-15 14-30 Team standup.md.

Date and time tokens

These tokens are replaced with values from the session’s start time:

Token	Description	Example
YYYY	4-digit year	2024
MM	2-digit month, zero-padded	03
DD	2-digit day of month, zero-padded	15
HH	2-digit hour (24-hour clock), zero-padded	14
mm	2-digit minute, zero-padded	30
ss	2-digit second, zero-padded	07

Session tokens

Token	Description	Example
{{title}}	Session title	Team standup
{{sessionId}}	Full session UUID	550e8400-e29b-41d4-a716...

Token format note

Date/time tokens use bare uppercase/lowercase letters (YYYY, MM, HH, mm). Session tokens use double-brace Handlebars-style syntax ({{title}}, {{sessionId}}). These are distinct formats — both are supported in the same template.

Note that mm (lowercase) is minutes and MM (uppercase) is months. Be deliberate with case.

Examples

Template	Output
YYYY-MM-DD HH-mm {{title}}	2024-03-15 14-30 Team standup
{{title}} — YYYY-MM-DD	Team standup — 2024-03-15
YYYY/MM/DD/{{sessionId}}	2024/03/15/550e8400-...
{{title}}	Team standup

Collision handling

If a file with the generated name already exists in the export folder, Quendian appends a counter: filename (2).md, filename (3).md, etc.

Empty template behavior

If the template produces an empty string after substitution (for example, {{title}} with an untitled session), Quendian falls back to meeting-{sessionId} to ensure a valid filename is always produced.

---

Token list sourced from CompletedSessionStore.swift — audited 2026-05-10.