Clear Figma export clutter from your Downloads folder

why your Downloads folder fills up so fast

Figma has no native prompt to choose where exports land. Unless you've changed your browser or OS download settings, every file goes to the same place: Downloads. One export cycle adds a handful of files. A week of active design work can add hundreds.

The problem compounds because most designers never delete as they go. The export is a means to an end — you grab the file, upload it somewhere, and move on. Cleanup feels like extra work, so it waits. Then it waits longer.

The result is a folder that functions as a graveyard. Files from six projects back sit alongside assets you exported this morning. There's no signal for what's current, what's been used, or what can safely go.

how to find and delete old Figma exports

Start with a search. On macOS, open Finder, navigate to Downloads, and sort by "Date Added" descending. On Windows, open File Explorer and sort by "Date modified." This surfaces the oldest files first — the ones most likely to be redundant.

Next, filter by file type. Figma exports are almost always PNG, JPG, SVG, or PDF. Search for each extension in turn. Anything older than 30 days with no clear project association can almost certainly go.

If you want to move faster, tools like Gemini (macOS) or Duplicate File Finder identify exact duplicates by hash — useful when you've exported the same asset multiple times at the same scale. These tools remove the guesswork from bulk deletion.

One rule worth setting: don't delete until you've checked your destination. If you exported a file and uploaded it to Google Drive, confirm it's there before clearing it locally. Five seconds of verification prevents losing work you can't regenerate quickly.

how to stop Figma exports from cluttering Downloads in the first place

The cleanest fix is to change where exports land. In Chrome, go to Settings → Downloads and enable "Ask where to save each file before downloading." Every Figma export will now prompt for a destination. It adds one step, but that step gives you control.

If you'd rather not be prompted every time, create a dedicated folder — something like Figma Exports or Design Assets — and set it as your default download location. This at least isolates the clutter from the rest of your Downloads and makes batch cleanup easier.

A third option: schedule a weekly five-minute sweep. Every Friday, sort by date, delete anything older than the current week that's already been uploaded or handed off. Small habit, significant difference over time.

does changing your download folder actually fix the habit?

Partially. It reduces the spread of files and makes cleanup easier to batch. But it doesn't address the root cause: the export still lands on your machine first. You still have to move it. You still accumulate local copies of files that live somewhere else.

The friction shifts rather than disappears. A dedicated exports folder is tidier than Downloads, but it requires the same manual upload step afterward — and it introduces a new place to forget files.

For designers who export frequently, the folder management problem is a symptom. The underlying issue is a workflow built around a local intermediary that serves no real purpose. The file's destination is Google Drive. The local copy is just overhead.

what a Drive-first export habit actually looks like

A Drive-first habit means the export goes directly to its destination — no local stop, no manual upload, no cleanup later. The Downloads folder is never involved.

This is what exporting from Figma directly to Google Drive looks like in practice. You select your assets, choose a Drive folder, and export. The file appears in Drive. Nothing lands on your machine.

The habit change is minimal — you're still clicking export. The difference is where the export goes. But that difference eliminates the entire cleanup problem: no local files means no folder bloat, no duplicate management, no Friday sweeps.

ExportHub is a Figma plugin built specifically for this. It connects Figma to Google Drive directly, lets you select a destination folder or create a new one, rename assets before export, and manage multiple Google accounts — all without leaving Figma. Get the free plugin and stop exporting to Downloads entirely.

should you clean up before switching workflows?

Yes — one clean sweep before you change habits means you're starting from zero. It also makes it easier to notice the difference. If your Downloads folder stays empty for two weeks after switching to a Drive-first workflow, you'll feel the change concretely.

Sort Downloads by file type, delete old exports in bulk, and confirm anything you need is already in Drive. The whole process takes under 15 minutes for most designers. After that, you don't need a system for managing local exports because you stop generating them.

If you work on a team, it's worth aligning on this before switching. A shared Drive folder structure combined with a plugin like ExportHub means everyone exports to the same place, named consistently, without a local file ever entering the picture. The export-download-upload loop slows teams down not just individually but collectively — broken handoffs, stale files, version confusion. Removing the local step fixes all of it at once.