Filename Patterns
Custom filename patterns let you define exactly how exported files are named, using tokens that are replaced with page-specific values at export time.Available Tokens
Tokens are slugified automatically — spaces become hyphens, special characters are removed.
Default Pattern
By default, the exporter uses{title} as the filename pattern, producing files like:
Custom Patterns
Combine tokens and static text to build a pattern that fits your workflow:
Rule: The pattern must include at least
{title} or {id} to guarantee unique filenames across the export.
When to Use Custom Patterns
{date}-{title} — Best for blogs, changelogs, or any content where chronological ordering matters. Files sort lexicographically by date.
{title}-{id} — Best for large spaces where page titles might not be globally unique. The ID suffix guarantees uniqueness.
{id}-{title} — Useful when importing into a system that uses Confluence page IDs as a primary key.