Naming presets

Create reusable naming presets with a filename format or written instructions for consistent filenames.

6 min readUpdated Jul 20, 2026Get Started
~/InvoicesFilename format
scan_001.pdf2024-03-14_Amazon_INV-4711.pdf
IMG_2042.pdf2024-03-12_Uber_INV-3392.pdf
document (3).pdf2024-03-09_Notion_INV-8821.pdf
receipt.pdf2024-03-05_Figma_INV-1567.pdf
invoice_final_v2.pdf2024-02-28_Adobe_INV-9043.pdf

Naming presets are saved naming setups: define one once and NameQuick applies it to every similar file.

There are two kinds, and both produce structured, consistent names:

  • Filename formats: build the name visually from fields like "Invoice Date" or "Vendor Name". Precise and predictable.
  • Written instructions: describe the naming in plain language, like "name this with the date and topic". Flexible when you'd rather describe than build.

Need a quick one-off? Smart Rename names files with zero setup. Rename Modes decide whether names apply instantly or wait for your review.


Filename formats#

Filename formats give you precise, visual control over the naming. You define what to extract, and NameQuick builds filenames that always follow your format.

New filename format

Preset name

Fields

Choose the details you want NameQuick to find.

Purchase Date
Merchant
Total Amount
Optional
Document Type
Custom

Suggested fields

Invoice Date Invoice Number Vendor Name Due Date Tax Amount Subtotal
Filename format

Choose what appears in the final name

Drag to reorder. Click a separator to change it.

Purchase Date _ _ Merchant _ _ Total Amount _ _ Document Type _ Add part
Text cleanup

Apply your naming convention

Remove leading and trailing spaces
Scope: All fields
Format date as YYYY-MM-DD
Scope: Purchase Date
Use Title Case
Scope: Merchant
Format currency amount consistently
Scope: Total Amount
Conditional name parts
Add a name part only when a condition matches
Test

Live preview as you edit

Originalscan_001.pdf
Generated2024-03-14_Uber_Technologies_24.50_Receipt.pdf

Extraction Fields#

Fields are the heart of a filename format. You write them in plain English, and the AI uses your field names as extraction instructions.

Fields

Choose the details you want NameQuick to find.

Invoice Date
Vendor Name
Invoice Number
Due Date
Optional

Suggested fields

Total Amount Tax Amount Subtotal Document Type Purchase Date Merchant

Good field names are specific:

Too vagueSpecific (what to extract)
DateInvoice Date
AmountTotal Amount Due
NameVendor Name
NumberInvoice Number

Give hints when helpful:

  • "Invoice number (usually starts with INV-)"
  • "Date the document was signed"
  • "Total including tax, formatted as currency"

The more specific your field names, the better the extraction. The AI reads them as instructions for what to find.

The format builder#

A filename format uses a visual builder with drag-and-drop pills. Drag to reorder the parts, and click a separator to change it.

Filename format

Choose what appears in the final name

Drag to reorder. Click a separator to change it.

Invoice Date _ _ Vendor Name _ _ Invoice Number _ Add part
Originalscan_001.pdf
Generated2024-03-14_Amazon_INV-4711.pdf

Three pill types:

Invoice Date
Extracted field
A value the AI reads from your file
{date}
System placeholder
A built-in token like {date}, {year}, or {counter}
Invoice-
Custom text
Literal text you type into the name

Written instructions#

Written instructions let you describe the naming in plain language. Instead of building a format from fields, you tell NameQuick what the result should contain. They work well when you would rather describe the result than assemble it field by field.

New written instructions

Preset name

Instructions
341 characters
Test with a file
This is a preview. Your files won't be renamed yet.
OriginalIMG_4823.jpg
Generatedparis-skyline-sunset.jpg

Creating a naming preset with written instructions:

  1. Open the sidebar and go to Naming Presets
  2. Click New and choose Written Instructions
  3. Write the naming instructions in your own words
  4. Preview on sample files, then save

Your instructions can be as short or detailed as you need. One naming preset can define different formats per document type, formatting rules, and edge-case handling. The AI reads the full instructions and applies the matching rules to each file.

A more detailed example. These invoice instructions set a naming format, per-document-type rules, and edge cases:

New written instructions

Preset name

Instructions
659 characters
Test with a file
This is a preview. Your files won't be renamed yet.
Originalscan_2843.pdf
Generated2024-03-14_Amazon_INV-4711_49.90EUR.pdf

For filename values that are not printed on the document, like ISO week codes or customer codes, see Teach the AI your naming convention.


Text Cleanup#

Text cleanups modify extracted values after AI extraction but before the filename is assembled. You write them in natural language.

Field-specific cleanups apply to individual values (e.g. "Format invoice date as YYYY-MM-DD"). Global cleanups apply to the assembled filename (e.g. "Replace all spaces with hyphens"). Field cleanups run first, then the pattern assembles, then global cleanups run on the result.

Text cleanup
reformat date to DD-MM-YYYY
March 15, 202415-03-2024
Title Case
amazon inc.Amazon Inc.
replace spaces with dashes
Amazon IncAmazon-Inc
remove special characters
INV#4711INV4711
remove decimals from price
$299.50$299

Testing and Iterating#

Before applying a filename format to real files, test it:

  1. Open your naming preset in the editor
  2. Drop a sample file into the test area
  3. AI extraction runs in preview mode (no renames consumed)
  4. See the result: Original filename → Generated filename
Try it with a file
Original:afdsasd.pdf

Use the test area to check whether your preset produces the filenames you expect. If a field extracts the wrong value or the format is off, adjust field names to be more specific, add text cleanups for formatting, or try different sample files. Iterate until the output matches what you need.


Reference#

System Placeholders#

System placeholders insert metadata that does not need AI extraction:

CategoryPlaceholders
Date/Time{date}, {time}, {datetime}, {year}, {month}, {day}, {hour}, {minute}, {second}
File Info{original}, {extension}, {parent}, {size}, {dimensions}, {created}, {modified}, {accessed}
Sequence{counter}

Date formatting:

Customize date format with a colon:

Terminal
{date:yyyy-MM-dd}      → 2024-03-15
{date:MM-dd-yyyy}      → 03-15-2024
{date:yyyyMMdd}        → 20240315
{datetime:yyyy-MM-dd_HH-mm}  → 2024-03-15_14-30

Separators#

Each gap between pills can have its own separator (underscore _, hyphen -, period ., space, double underscore __, double hyphen --, no separator, or a custom string). You can also customize how multi-word values appear within each field by clicking the separator indicator on a teal user field pill.

Example: If AI extracts "Acme Corporation":

Word SeparatorResult
UnderscoreAcme_Corporation
HyphenAcme-Corporation
PeriodAcme.Corporation
SpaceAcme Corporation
Double UnderscoreAcme__Corporation
Double HyphenAcme--Corporation
NoneAcmeCorporation

Advanced Features#

Field Conditions let you extract a field only when a condition is true. For example, only add a "PRIORITY" prefix when the invoice amount exceeds $10,000. If the condition is false, the field is skipped.

Fallback Chains define multiple extraction attempts when extraction might fail. For example: first try "Extract company name from letterhead", then "from signature block", then "any company name mentioned". The first successful extraction wins. If all fail, a default value is used.

Computed Fields derive values from other fields without additional AI calls. For example, concatenate first_name and last_name into a Full Name field.

Filename format rules#

Filename format rules apply logic during filename generation. They are different from file organization Rules: filename format rules modify the name, not the file location. Each rule has a condition, an action, and a point at which it runs.

Example: Priority Invoice Prefix

Add "PRIORITY-" to invoices over $10,000:

  • Condition: invoice_amount is greater than 10000
  • Action: Add prefix "PRIORITY-"

Result: PRIORITY-2024-03-15_Amazon_INV-4711.pdf

Example: Skip Field When Empty

Don't include purchase order number if it doesn't exist:

  • Condition: po_number is empty
  • Action: Skip field
AspectFilename format rulesDocument Rules
PurposeModify filename generationOrganize files on disk
ActionsTransform, prefix, skip fieldsMove, tag, archive, trash
ScopeInside a filename formatAcross Watch Folders

Use filename format rules for naming logic. Use Document Rules for file organization.


Automation#

Combine naming presets with Rules for fully automated workflows:

  1. Set up a Watch Folder for incoming files
  2. Assign your naming preset as the processing mode
  3. Add rules to organize files after renaming

New files are renamed automatically using your naming preset, then moved to the right folders based on extracted values.


FAQ#

Can I switch from written instructions to a filename format? Not automatically, but you can use written instructions to learn what structure works for your files, then create a filename format with those fields.

What if the AI can't extract a field? If a required field is missing, the rename is blocked to prevent incomplete filenames. Use fallback chains or mark fields as optional to handle edge cases.

Do text cleanups use AI? Text cleanups are sent as instructions to the AI alongside extraction. They're processed in the same API call, not separately.

Can I use both AI fields and system placeholders? Yes. Mix them freely: {Vendor Name}_{date}_{Invoice Number}

Related guides

Try it yourself

Self-managed: 50 renames in the app. Managed trial starts in checkout.

★★★★★
Joinhappy customers