
Figma's export Suffix field appends text to an exported filename without requiring a layer rename. Use it to distinguish delivery variants, then check the saved files and their settings. A suffix is an identifier; it does not verify that the right crop, profile, or format was exported.
Key Takeaways
- Export suffixes can label variants while source layer names stay stable.
- Choose suffixes that identify a real difference the recipient needs.
- Check for ambiguous or conflicting filenames before sending the package.
Name the distinction before the file
Begin with the delivery brief. A shop owner may need a transparent product cutout, a flattened marketplace image, and a small review preview. Those are useful distinctions. Labels such as “final2” and “newest” lose meaning as soon as another revision appears.
For a hypothetical ceramic collection, a source frame might be called “BlueCup.” The deliverables could use suffixes that identify background or purpose. Agree on that vocabulary with the recipient so a short name remains understandable outside the Figma file.
Retain the source naming scheme if it already supports the team's workflow. Renaming layers purely to alter exported filenames can make comparisons and review notes harder to follow.
Apply the suffix in export settings
Figma's export documentation explains that text entered in Suffix is appended to the exported asset name. Its example demonstrates that the field adds the entered text, rather than interpreting it as a new layer name.
Choose the relevant frame and inspect each export configuration. Enter the required suffix and confirm the format and scale alongside it. Include any separator you want in the suffix itself, and inspect the actual saved name rather than relying on an assumed filename convention.
Do not change a source asset's path without considering linked projects. The missing-linked-images guide explains why filenames and locations can matter to another application's package.
Match names to actual outputs
Make a small delivery list before exporting the whole collection. For each item, record the intended use, source frame, format, and suffix. Open a representative file from each variant and confirm its dimensions, background, and visible content.
For the cup example, a file labelled as a cutout should actually have the required transparent region. A name containing “small” should correspond to the requested smaller rendition. These are proposed checks; the suffix field does not enforce their meaning.
If the work involves repeated personalized designs, preserve the source data separately. Naming exports does not restore missing variable-template source images.
Review the final package
Look for duplicate names that could overwrite one another during an ordinary file copy. Confirm that the recipient can distinguish versions without opening every image. For a marketplace bundle, check the destination's file packaging limits as a separate requirement.
Acceptance means that every promised variant exists, its name identifies its role, and its actual content matches that role. This naming workflow is documentation-based and does not claim that a particular batch was exported or uploaded.
Related tasks
- Why Are Images Missing When Someone Else Opens My InDesign or Photoshop Project?
- Why Does a Reopened Photopea Variables Template Say Its Source Images Are Missing?
- How Do I Package an Etsy Digital-Art Bundle Without Losing Print Versions?
Sources and scope
- Export formats and settings for static designs: Suffix-based file identity in review deliveries.
Documentation-based guidance. Examples and acceptance checks are proposed, not measured software tests.
Prepared by Imagild Editorial, the company editorial team responsible for these guides. AI assisted research and drafting. This is documentation-based guidance with proposed examples, not a claim of hands-on testing or an independent product review. Report a correction.
Cover: AI-generated conceptual editorial illustration; not a real application screenshot, observed output or before-and-after test.