Naming Convention

Naming Convention lets you create custom file naming templates using dynamic values like project name, prompt, date, tool, and format. You can set an organization-wide default and optionally override it at the project level.

Available for Pro, Business, and Enterprise users.

In this article

• Availability
• How it works
• Set up organization defaults
• Set up project-level naming
• Template builder and live preview
• Available tokens
• Formatting rules
• Saved templates
• Custom fields
• Sequence settings
• Enterprise permission control
• Default behavior
• Who can edit naming settings
• Common questions

Availability

Free, Essential, Premium, and Premium+ plans do not have access to Naming Convention.

How it works

Naming Convention uses a two-level system:

• Organization preferences define the default naming convention that applies to all downloads across your account.
• Project settings can override the organization default for a specific project, when permissions allow it.

When you download a file, Magnific checks whether the current project has its own naming convention. If it does and the user is allowed to use it, that template is applied. Otherwise, the organization default is used. If no custom naming exists at either level, the built-in system default is used.

Set up organization defaults

Organization defaults apply to all downloads unless overridden at the project level.

1. Go to organization preferences

   Open your account settings and navigate to the Naming Convention section.

2. Create or edit your template

   Use the template builder to define your naming structure with tokens.

3. Choose formatting options

   Set separator, case, and maximum length.

4. Define custom fields if needed

   Add labels and default values for fields like client code, department, or campaign.

5. Save

   Your organization default is now active. All downloads will follow this template unless a project overrides it.

Set up project-level naming

Projects can use the organization default or define their own naming convention.

1. Open a project

   Navigate to the project you want to customize.

2. Go to project settings

   Open the Naming Convention section.

3. Choose your mode

   Select whether to use the organization default or create a custom naming convention for this project.

4. Define the template and project values

   If using custom naming, set the template and fill in any project-specific values.

5. Save

   Downloads from this project will now use the custom naming convention.

Enterprise restriction

In some Enterprise organizations, admins can disable project-level naming customization for members. If you cannot edit naming in a project, contact your organization admin.

Template builder and live preview

The template builder lets you construct file names by combining dynamic tokens. As you add or reorder tokens, a live preview shows how the final file name will look before you save.

This helps you verify the result in real time without downloading a test file.

Available tokens

Tokens are dynamic values that are automatically replaced with real data when a file is downloaded. You can build templates using the following token categories:

If a token has no value at download time, it is skipped automatically. No extra separators are added.

Formatting rules

You can configure how the final file name is formatted:

• Separator: underscore, dash, or custom character
• Case: UPPERCASE, lowercase, or Title_Case
• Max length: 255 characters. Longer values are shortened automatically, starting with the prompt field
• Special characters: removed automatically for file system safety
• Required: at least one identifying token must be included in the template

Saved templates

You can save multiple naming templates for different use cases. Templates make it easy to switch between naming formats for different workflows, clients, or delivery types without rebuilding the template each time.

Custom fields

Organizations can define custom field labels and default values that members can use in naming templates. Custom fields let you include structured information like client code, department, campaign name, or any other internal label directly in file names.

Sequence settings

You can define how sequence numbers behave in your naming template, including starting number and padding. Sequence settings are useful for versioned exports, batch downloads, or any workflow where files need to be numbered consistently.

Enterprise permission control

Enterprise admins can decide whether members are allowed to customize naming at the project level.

• If enabled, members can create project-specific naming conventions.
• If disabled, all downloads follow the organization naming convention. Project settings show a locked state for affected members.

Default behavior

If no custom naming rule is configured at either the organization or project level, downloads use the built-in default format:

magnific_prompt_timestamp.format

This is the system fallback until a user or organization sets a custom template.

Who can edit naming settings

Organization settings

Project-level settings

Common questions

Can I customize how downloaded files are named?

Yes. Naming Convention lets you create custom naming templates for downloads. Available for Pro, Business, and Enterprise users.

Where do I configure Naming Convention?

Depending on your plan and role, you can configure it in organization preferences, project settings, or both.

What happens if I don't configure a custom template?

Downloads use the built-in default file naming format: magnific_prompt_timestamp.format.

Can a project use a different naming convention from the organization default?

Yes, if project-level customization is available for that user and organization.

Can all members edit organization naming settings?

No. In Business and Enterprise organizations, members can view but not edit organization preferences.

Why can't I customize naming in my project?

In some Enterprise organizations, admins can disable project-level naming customization for members. Contact your organization admin to check your permissions.

What happens if a token has no value?

Empty values are skipped automatically so file names stay clean. No extra separators are added.

What happens if the file name is too long?

The system shortens longer values, starting with fields like prompt, to keep the filename within the allowed limit of 255 characters.

Can I rename previously generated files?

Yes. Any naming rules you create will also apply to files that were generated before the rule was set, if you download them after setting the rule.