why Figma exports go to your Downloads folder

why does Figma export to Downloads by default?

Figma runs in the browser. When you hit Export, Figma packages your assets and hands them to the browser as a file download — the same mechanism that handles any file you download from the web. The browser then saves that file to whatever its default download location is set to, which on almost every machine is the Downloads folder.

Figma has no native access to your file system. It cannot browse folders, remember a preferred destination, or write directly to a path you choose. Every export goes through the browser's download pipeline. That pipeline drops files in one place.

The Figma desktop app behaves slightly differently — it can prompt you to choose a save location — but the default behavior remains the same unless you change it manually in your browser or OS settings. Most designers never do.

what's the actual cost of this behavior?

Each export creates a small detour. You export from Figma, switch to Finder or File Explorer, locate the file in Downloads, then drag or upload it wherever it actually needs to go — usually Google Drive, Slack, or a shared folder. That detour takes between 30 seconds and a few minutes depending on how organised your Downloads folder is.

Multiply that across a typical workday. Designers working on live projects export dozens of assets — icons, illustrations, UI screenshots, handoff specs. Each one follows the same path. The time adds up fast, but the friction compounds faster. Every context switch interrupts focus. Every detour is a moment where you're not designing.

There's also a secondary problem: Downloads folders accumulate. Assets pile up without structure — multiple versions of the same file, exports you forgot to move, renamed duplicates sitting next to originals. Finding the right file later becomes its own task.

why doesn't Figma just let you choose a folder?

Browser security models deliberately restrict web apps from accessing the local file system. This is intentional — it prevents malicious sites from reading or writing to arbitrary locations on your machine. Figma operates within those same constraints.

The File System Access API, supported in Chromium-based browsers, does allow web apps to request folder access with explicit user permission. Figma has not implemented this for exports, and there's no public indication they plan to. For now, every export goes through the browser download channel.

The desktop app has more flexibility because it's an Electron wrapper with deeper OS integration. But even there, most users work with default settings and never redirect exports to a specific project folder.

can you change where Figma exports files?

You can change the browser's default download location in settings. In Chrome, that's Settings → Downloads → Location. In Safari, it's Preferences → General → File download location. This changes where all downloads land, not just Figma exports — which creates its own problems if your Downloads folder serves other purposes.

You can also enable "Ask where to save each file before downloading" in most browsers. This prompts you to choose a destination every time. It's more flexible but adds a click to every export and doesn't solve the underlying context switch — you're still navigating your file system manually each time.

Neither approach gets assets into Google Drive automatically. Both require you to move files after the fact.

why the default export path matters more for Drive-heavy workflows

If you store assets in Google Drive — and most design teams do — the local Downloads folder isn't a destination, it's a waypoint. Nothing that lands there is actually accessible to collaborators until you move it. That creates a two-step process that can't be shortened within Figma's native export flow.

The only way to eliminate the detour entirely is to skip the local file system altogether. That means exporting directly from Figma to Drive — bypassing Downloads, bypassing manual uploads, and cutting the workflow down to a single action.

That's what exporting Figma assets directly to Google Drive makes possible — no local file created, no folder navigation, no upload step. The asset goes from Figma to Drive in one click.

If you're also making format decisions at export time, understanding whether to export PNG or SVG for Google Drive becomes relevant before you set up that workflow.

the default isn't going away

Browser architecture won't change to give web apps unrestricted file system access — that would introduce unacceptable security risks. Figma won't redesign its export pipeline for a single cloud storage provider. The Downloads folder default is structural, not accidental, and it will remain the default for the foreseeable future.

Working around it at the browser or OS level reduces some friction but doesn't solve the Drive handoff problem. The most direct fix is a plugin that handles the transfer — one that replaces the download step entirely rather than reshuffling it.

ExportHub connects Figma directly to Google Drive. Select your assets, pick a destination folder, and export. Nothing touches your Downloads folder. Get the free plugin and remove the detour for good.