Create a new Google Drive folder from inside Figma

why folder creation matters at export time

Most designers don't think about folder structure until after the export. Assets land in Downloads, get uploaded to Drive in a batch, and then get sorted — or don't. That's a two-step problem: the upload friction and the organisation debt it creates.

Creating a folder at the moment of export solves both. You name it with the project context fresh in mind, assets land exactly where they belong, and nothing needs to be moved later. The Figma export loop already costs teams more time than it should — disorganised destinations compound that.

how to create a new google drive folder from inside figma

ExportHub surfaces folder creation directly in the destination step of the export flow. Here's the full sequence:

1. Open ExportHub in Figma via the plugins menu.
2. Select the assets or frames you want to export.
3. In the destination panel, browse to the Google Drive location where the new folder should live.
4. Click New folder, type the folder name, and confirm.
5. The new folder is created in Drive immediately and selected as the export destination.
6. Click export — assets go straight to the new folder.

No page refresh, no switching to Drive, no duplicating an existing folder and renaming it. The folder exists in Drive before the export runs, so assets land in the right place on the first try.

can you create nested folders during export?

Yes. ExportHub lets you navigate your existing Drive hierarchy before creating the new folder, so you can place it inside a client folder, a project folder, or any subfolder you already have. If you're maintaining a consistent Drive folder structure across design handoffs, this keeps new exports consistent with that pattern without extra steps.

There's no limit on nesting depth. If your Drive is organised as Clients → [Client Name] → [Project] → Assets, you navigate to Assets and create the sprint or date-specific subfolder right there.

what happens if the folder already exists?

ExportHub lists your existing folders as you navigate, so you'll see the folder before creating a duplicate. If a folder with the same name already exists at that level, you can select it instead. Google Drive itself allows multiple folders with identical names — ExportHub doesn't prevent that — so naming discipline on your end matters. Consistent naming conventions pay off here; see the post on naming Figma export batches for Google Drive for practical conventions.

why not just create the folder in drive first?

You can — but it costs you a context switch. Opening Drive, navigating to the right location, creating the folder, switching back to Figma, then running the export adds 60–90 seconds to what should be an instant action. Multiply that by every sprint, every handoff, every client revision cycle, and the time lost is real.

More importantly, folder names created outside of the export moment are often vague. "New folder" renamed to "v3 final" happens because the designer was in Drive, not in the project context. Creating the folder from inside Figma — with the assets selected and the project in view — produces better names and better structure.

how does this compare to the manual export workflow?

The standard Figma export sends files to your local Downloads folder. From there, you upload to Drive, navigate to the right location, and move files into the correct folder — or create one if it doesn't exist. That's at minimum four separate actions after leaving Figma.

With ExportHub, folder creation, destination selection, and export happen in a single plugin interaction. Assets go directly from Figma to the correct Drive folder. The export without downloading locally post covers the full comparison of the two workflows.

does creating a folder require special google drive permissions?

ExportHub requests the necessary Drive permissions during the OAuth connection step. Standard Google Drive accounts — personal or Workspace — allow folder creation for authenticated users. If your Workspace account has restricted permissions set by an administrator, creating folders may be blocked in specific shared drives. In that case, creating the folder manually and selecting it as the destination still works. For more on how the plugin connects to Drive, see Connect a Figma plugin to Google Drive: OAuth and folders.

using folder creation with multiple google accounts

ExportHub supports multiple Google accounts within the same session. If you export client work to separate Drive spaces, you can switch accounts and create folders in each one independently. The folder creation UI reflects whichever account is active at export time. This is useful for agencies managing several client accounts — each client's exports go to their own Drive with the correct folder structure, without logging out and back in.

Account switching and folder creation together cover the two most common handoff friction points. See Switch Google accounts in a Figma plugin for separate client Drive spaces for the full account-switching walkthrough.

tips for consistent folder naming from figma

Folder names created at export time should be immediately readable to anyone with Drive access — including developers, clients, and teammates who weren't in the Figma session. A few principles that hold up in practice:

• Use dates in ISO format: 2025-06-17 not June 17 or 17-06. Sorts correctly, reads unambiguously.
• Include the deliverable type: icons, screens, specs, illustrations. A flat list of dated folders with no type context is hard to navigate quickly.
• Avoid version suffixes unless the version has meaning: v3 alone is noise. v3-client-approved is useful.
• Match the folder name to the Figma page or section you're exporting from. Consistency between the source file and Drive structure reduces handoff confusion.

If your team exports in batches with multiple asset types per export, consider a parent folder per session with subfolders by type. You can create both layers inside ExportHub without touching Drive directly.

get exporthub

ExportHub is a free Figma plugin. Install it from the Figma Community and connect your Google account to start exporting directly to Drive — with full folder creation and destination control built in. Get the free plugin.