Batch rename Figma assets before Google Drive export

why asset names matter before they reach Google Drive

A file named Group 84.png is useless the moment it leaves your hands. Whoever opens your Google Drive folder — a developer, a client, a teammate — has to guess what it is, rename it themselves, or ask you. That last step costs more time than the export ever saved.

Renaming after export compounds the problem. You're working outside Figma, across multiple files, in a folder that may already contain previous versions. Mistakes compound: files get overwritten, version suffixes get applied inconsistently, and nothing matches the component names in your design system.

Fixing names at the source — inside Figma, before the export runs — eliminates the downstream problem entirely. It also enforces consistency across every handoff, not just the ones where someone remembered to rename.

how does Figma determine export file names?

By default, Figma names exported assets after the layer or frame they belong to. If your layer is named Button/Primary/Default, the exported file becomes Button_Primary_Default.png. If it's still called Frame 3, that's exactly what lands in your Drive folder.

Figma respects slashes in layer names as path separators for some formats, but for most export scenarios — particularly batch exports — what the layer is called is what the file is called. That makes layer naming the most reliable point of control.

Suffixes set in Figma's export panel (like @2x or _dark) append to the layer name. They don't replace it. So a well-named layer with a clear suffix produces a clean, descriptive filename. A poorly named layer with a suffix produces a slightly longer mess.

what are the options for batch renaming Figma layers before export?

There are three practical approaches, each with different tradeoffs.

Manual rename in the layers panel. Select a layer, press ⌘R (Mac) or F2 (Windows), and type a new name. Works for one or two assets. Does not scale to batches.

Figma's built-in batch rename. Select multiple layers, right-click, and choose "Rename layers." Figma opens a rename dialog that supports find-and-replace, prefix and suffix additions, and sequential numbering. This is the fastest native option for renaming a consistent set of layers before running an export. It handles batches well as long as your naming pattern is predictable.

Rename inside a plugin at export time. Some export plugins — including ExportHub — let you edit asset names at the point of export, without touching the underlying layer names in Figma. This is useful when you want to keep original layer names intact in the file but export with different names for a specific deliverable. You adjust the name, export, and the layer in Figma stays unchanged.

how to use Figma's built-in batch rename before exporting

Select all the layers or frames you intend to export. You can do this from the canvas with a drag selection, or from the layers panel with ⌘ or Shift click. Once selected, right-click any selected layer and choose "Rename layers."

The dialog gives you a text field where you can type the new name directly, or use these variables:

• $n — sequential number starting from 1
• $N — sequential number padded with zeros (01, 02, 03)
• $* — the current layer name

A pattern like icon-$N produces icon-01, icon-02, icon-03 — clean, sequential, ready for a developer's icon kit. A pattern like brand-$* prepends a project prefix to every existing name without losing what it was called.

Once you confirm the rename, run your export. The names you set are what arrive in Google Drive.

when should you rename at export rather than in the layers panel?

Renaming layers in Figma is permanent. If your file is shared and others rely on those layer names for auto-layout, component references, or developer inspect, changing them to suit an export creates conflicts.

In those cases, renaming at export time is safer. ExportHub lets you edit the filename for each asset in the export queue before anything is sent to Drive. The layer name in Figma stays exactly as it is — only the exported file gets the adjusted name.

This is particularly useful for client-facing deliverables. A component called CTA/Filled/Hover in your system might need to export as button-hover-state.png for a client's asset library. You make that change once in the export panel, and it doesn't touch your Figma file structure.

how to set a naming convention that survives multiple export rounds

Naming discipline compounds over time. A convention set in the first sprint still works in the tenth if everyone follows it. A few principles that hold up in practice:

Use kebab-case. Lowercase, hyphen-separated names (icon-arrow-right) are safe across operating systems, readable in URLs, and consistent with how most front-end codebases reference assets.

Include context in the name. button-primary-hover is unambiguous. button3 requires memory or context to decode. Google Drive search works on filenames — descriptive names make retrieval faster.

Version suffix for iterative exports. If you export the same asset across multiple rounds, append -v2 or a date (-20260601) rather than overwriting. This pairs well with naming Figma export batches for developers, which covers handoff-specific conventions in detail.

Match component names to export names where possible. The less translation required between Figma and Drive, the fewer errors. If your component is icon/arrow/right, the export target should be icon-arrow-right — not asset-final-USE-THIS-v3.

how ExportHub handles renaming in the export flow

ExportHub is a Figma plugin that exports assets directly to a Google Drive folder without a local download step. As part of that flow, it surfaces each asset's name before the export runs — giving you a chance to edit, confirm, or adjust naming without leaving the plugin.

You select the assets, choose your Drive destination, edit any names in the queue, and export. Files arrive in the folder with the names you confirmed. No post-export renaming in Drive, no version confusion, no separate rename pass.

This fits naturally into the consideration stage of the export loop: the moment between "I've selected what to export" and "I've pushed it to the right folder." That window is where naming should happen — and ExportHub keeps it inside Figma rather than pushing it downstream. If you haven't tried it yet, the plugin is free — see how Figma to Google Drive in one click works in practice.

For teams already managing a structured Drive handoff folder, renaming at export time slots directly into that workflow. The Google Drive design handoff folder structure for agencies post covers how folder organisation and naming conventions work together.

does renaming in Figma affect anything else in the file?

Renaming a layer changes how it appears in the layers panel, in developer inspect, and in any component that references it by name. In a tightly built design system, this can break things — variants reference their layer names, auto-layout constraints can be name-dependent in some plugin ecosystems, and developers scanning inspect panels rely on seeing the names they expect.

For standalone frames and exported assets that aren't part of a component structure, renaming is low-risk. For anything inside a component or variant set, prefer renaming at export time rather than in the layer itself.

The Figma export scale and suffix guide covers how suffixes interact with layer names and export settings — worth reviewing if you're building a repeatable multi-scale export workflow.

a practical pre-export naming checklist

Before running any export to Google Drive, run through this list:

• Are all selected layers named — not defaulting to "Frame," "Group," or "Component"?
• Do the names use a consistent format (kebab-case, snake_case, or whatever your project uses)?
• Do names include enough context to be understood without opening Figma?
• If exporting multiple scales, are suffixes applied and correct?
• If files from a previous round exist in the Drive folder, are new names differentiated by version or date?

Running this once before a large export takes under two minutes. Fixing naming errors in Drive after 40 files have landed takes considerably longer — and the cost of export clutter applies equally to Drive folders that accumulate unnamed assets over time.