123SUDODocs
Guides

Output file naming

Set the default for normal conversions and override it per flow on desktop and Android.

Open Settings → File naming on desktop or Android to set the default pattern and the policy for names that already exist.

This default applies to every normal conversion: quick convert, drag and drop, open-with or Android sharing, and bulk runs. The initial setting preserves the existing naming behavior; names do not change until you edit it.

Per-flow overrides

New flows start with Use the default (from Settings). Leave this selected to inherit Settings, or choose an explicit naming override. The flow summary shows which choice applies. Existing flows retain their saved naming choice.

Choose Keep name, Add suffix or Custom pattern on desktop and Android. Keep name preserves the original name without its extension; a suffix adds text to that name.

Build a pattern

Grouped placeholder buttons insert bracketed tokens. Try Name - Date, Name (counter) or Date - Name; a preset is selected only when its pattern matches exactly.

The live preview uses example data and updates as you edit. Patterns and file names remain left-to-right in right-to-left languages; translated labels do not change the tokens.

Supported placeholders

PlaceholderMeaning
[name]Original name without its extension.
[ext], [format]New extension without a dot; both tokens mean the same thing.
[date], [time]Local run-start date YYYY-MM-DD and time HH-mm-ss.
[year]Four-digit year.
[month], [day], [hour], [minute]Two-digit month, day, hour and minute.
[counter]Position within the run, starting at 1, padded to the batch-size digit count: 02 in a batch of 12.

All date and time tokens use the same local timestamp captured when the run starts. A new run starts a new counter.

Presets and examples

For an input named clip.mov, an MP4 output and the example run date:

PatternSaved file name
[name] - [date]clip - 2026-10-12.mp4
[name] ([counter])clip (02).mp4
[date] - [name]2026-10-12 - clip.mp4
[name].[ext]clip.mp4

Warnings and safe names

An unknown token such as [naem] stays literal and shows a warning. Check it before starting a conversion.

An empty result falls back to [name]. Names are sanitised for safe file-system use; a pattern creates a file name, not subfolders.

The output extension is lowercase and added automatically once when the pattern ends in .[ext] or .[format]. These tokens do not change the conversion format.

Desktop and Android use the same filename cleanup. Repeated matching output extensions are removed; empty or extension-only results fall back to the original name. Merge jobs retain the naming choice captured when added. Existing brace-token patterns remain supported.

Name conflicts

The If the name already exists setting offers Rename (choose another name), Overwrite (replace the existing file) and Skip (leave it alone). Rename is the initial policy; overwrite is never selected by default. Review this choice before converting important files.

On this page