Template Variables

Template variables insert information from each item, the current job, or the current date and time into filenames, folders, Apple Photos albums, and metadata text.

Where Variables Are Supported

Depending on the tool and destination, variables are available in:

• Ingest filename and destination templates
• Workflow subfolder, filename, and Apple Photos album templates
• Quick Transfer and Quick Rename templates
• IPTC template text fields

The variable picker in a template field shows the variables available in the current version of PhotoCuller.

Reusable Filename and Folder Templates

On Mac, open the { } menu beside a supported filename or folder field. Choose Save Current as Preset…, name the pattern, and save. Choose its name from the same menu to reuse it. Manage Presets… lets you edit, duplicate, rename, or delete patterns; manager edits save automatically.

On iPad and iPhone, use the bookmark menu in the template editor, or Settings > Filename & Folder Templates.

Filename and folder presets are separate. Choosing one copies its pattern into the field; later preset edits do not rewrite saved workflows. These presets store patterns, not the job values in a Session Variable Preset. Check the destination preview before running.

Basic Syntax

Put each variable in braces and combine it with static text:

{Year}/{MonthPadded}/{FileName}

Example output:

2026/02/DSCF1234

Native variable names are case-sensitive. In Filename, enter the filename stem only; PhotoCuller preserves or adds the appropriate file extension.

For capture-date variables, PhotoCuller uses the best date available in this order: EXIF capture date, IPTC date created, XMP create date, then the selected file’s creation date. Variables that require EXIF camera metadata remain unavailable when that metadata is missing.

Missing Values

In path and filename output, an unavailable variable normally resolves to Unknown. Use default when you need a different fallback:

{CameraModel | default:"NoCamera"}

You can mix variables and static text freely. Use / for nesting in Subfolder.

Practical Examples

Date and client folder structure

{Year}/{MonthPadded}-{MonthName}/{Session.Client}

Sequence-based delivery naming

{Session.Client}_{FullDate}_{Sequence}

High-speed sports naming

{FullDate}_{Session.ProjectName}_{TimeSort}{SubSecond | first:2}

Example output: 2025-04-05_Football_14304512

Mixed metadata naming

{CameraModel}_{ISO}_{FileName}

Variable Modifiers

Modifiers extract or transform part of a resolved value. Add them inside the braces after a pipe, in the order they should run:

{FileName | first:3 | upper}

For DSC_0001, this produces DSC.

Examples:

{FileName | first:8}
{Session.Client | replace:" " "_" | upper}
{CameraModel | default:"NoCamera"}

Use pad:N for leading zeros, where N is the minimum number of digits. For example, {ImageNumber | pad:3} turns 1 into 001 and 42 into 042. Values already at least N digits long are not shortened: 1234 stays 1234 with pad:3. A rename template such as Photo_{ImageNumber | pad:3} combines the grid’s image number with zero padding.

The variable picker includes a modifier editor, so you do not need to type modifier syntax manually.

Photo Mechanic Compatibility

PhotoCuller translates most common Photo Mechanic-style lowercase variables and legacy modifiers automatically. For example:

{year4}-{month0}-{day0}_{job}_{filenamebase:0,8}

is equivalent to:

{FullDate}_{Session.ProjectName}_{FileName | first:8}

Common Photo Mechanic aliases include {filenamebase}, {year4}, {month0}, {day0}, {job}, {model}, and {rating}. A few niche or application-specific Photo Mechanic variables are not supported, so always verify the live preview before running a production ingest or rename.

Inline Code Replacement Lookup

Look up a value from a named code replacement table with:

{CodeReplacement:TableName:Value}

Add #N to select a later TSV output column:

{CodeReplacement:cities:city_sf#2}

The lookup value can itself be a variable:

{CodeReplacement:clients:{Session.Client}}
{CodeReplacement:clients:{Session.Client}#2}

If the table or code is unavailable, the lookup token remains unchanged. See Code Replacements for table setup and delimiter-based replacements.

Capture Date and Time

These values describe the selected item’s best available capture date. Padded month and day variables are useful when filenames must sort chronologically.

Current Date and Time

These variables use the date and time when PhotoCuller renders the template, not the item’s capture date.

File and Item Properties

Folder and Path

These path variables are available for files opened from folders or mounted drives.

Camera and Capture Settings

Video Details

Use these variables to name or describe clips. Examples below show filename output.

Available values depend on the clip and source. Use a fallback such as {VideoFrameRate;Unknown} when a value may be missing. For capture date, camera, and location, use the existing date, camera, and GPS variables above and below. A Live Photo is still Photo for {MediaType}, even though it includes a video.

GPS and Location

GPS values come from EXIF. The Taken values come from the photo’s IPTC location fields.

Image Numbers

Use {ImageNumber} in rename templates, such as Photo_{ImageNumber}, to match filenames to the image numbers shown in the grid. Unlike {Sequence}, which generates an incrementing number for the current run or scope, {ImageNumber} uses the grid’s image number.

Sequence Variables

The Sequence starts at value controls both the first number and zero padding:

During a multi-source ingest, Sequence Scope controls whether {Sequence} and {Total} restart for each source or continue across the complete ingest. {IngestSequence} is unaffected by that setting: it advances once per selected source and remains the same for every item from that source.

Session Variables

Session variables are values you enter once for a job and reuse across all items. PhotoCuller detects the session variables used by a template and prompts for their values before running it.

You can also type a custom alphanumeric key such as {Session.Team}. PhotoCuller uses the key itself as the field label.

Session Variable Presets

Use the Presets menu in a Session Variables section to reuse values across jobs:

• Save Current as Preset… saves the currently filled non-empty values
• Update Current Preset overwrites the active preset
• Clear Values empties the current fields
• Manage Presets… lets you rename or delete presets and inspect their values

Applying a preset replaces the current session values with the preset’s saved values.

IPTC Date and Time

IPTC date-part variables use IPTC Date Created when present, falling back to the item’s best available capture date. {IPTC.DateCreated} itself is only populated when IPTC Date Created exists.

IPTC Content and Classification

Lists of keywords, codes, and names appear as text separated by commas.

IPTC Creator and Contact

{IPTC.Creator} uses the first creator name when the item contains more than one.

IPTC Locations, People, and Events

IPTC Rights, Releases, and Supply Chain

IPTC Products, Artwork, Registry, and Dimensions

IPTC AI and Provenance

See Also

• Code Replacements
• Ingest
• Workflows
• Quick Transfer and Rename
• IPTC Templates