Skip to content
BlurFirst

Blur Figma During Screen Sharing: Hide Unreleased Designs and Client Work

6 min read

Blur unreleased frames, client and project names, real data in mockups, and comments in Figma before a design review — with one caveat about the desktop app.

To hide unreleased designs and client work in Figma while screen sharing, run Figma in the browser at figma.com and use a browser extension like BlurFirst to blur specific frames, file names and mockup data before you present. The blur is painted into the tab as real pixels, so it holds on Zoom, Meet, Teams and Loom. One important note up front: this works on Figma in the browser — the standalone desktop app is a native window, so a browser extension cannot reach it.

What a Figma screen share can give away

Designers share Figma constantly — design reviews, stakeholder demos, client walkthroughs — and a single tab can expose far more than the one screen you meant to show. The canvas holds neighboring work, the chrome around it holds names, and the top bar holds your team. Before you present, plan to hide:

  • Unreleased designs and prototypes — frames for features that have not shipped, sitting one pan away from the frame you are presenting.
  • Client and project names — in the file browser, the browser tab title, the breadcrumb, and the pages and layers panel.
  • Real user data inside mockups — a dashboard design filled with real names, emails and financial figures instead of placeholder data.
  • Comments — comment pins and threads that show teammate names and candid, in-progress feedback.
  • Collaborator avatars — the multiplayer avatar cluster and live cursors that reveal exactly who is in the file.
  • File browser thumbnails — a grid of every project's cover image the moment you navigate back to Recents.

Browser Figma vs. the desktop app

This is the key limitation to plan around, so decide before the call. BlurFirst is a browser extension, so it applies to Figma running in a Chromium browser — Chrome, Edge, Brave or Opera — at figma.com. If you present from the Figma desktop app, it is a native window and the extension cannot paint into it. The fix is simple: for any screen share where privacy matters, open the file in the browser and share that tab. Everything else in this guide then applies exactly.

  1. 1

    Open Figma in the browser

    Go to figma.com in Chrome, Edge, Brave or Opera, open your file, and press Ctrl/⌘ ⇧ Y to start blurring.

  2. 2

    Blur off-screen and unreleased frames

    Use Element blur to click any frame or prototype you do not want seen; click it again to reveal it when you are ready to present it.

  3. 3

    Hide client names in the chrome

    Element-blur the file name in the tab bar, the breadcrumb, and the layers and pages panel so project and client names do not leak.

  4. 4

    Cover real data in mockups

    Box-blur the region of a dashboard mockup that holds real names, emails or financials while you show the layout around it.

  5. 5

    Mask comments and avatars

    Element-blur comment pins and the collaborator avatar cluster so teammate names stay private.

  6. 6

    Save a per-file profile and keep Panic ready

    Save a profile so the same frames and panels re-blur on load, and press Ctrl/⌘ ⇧ H to hide everything if you pan into unreleased work.

WhatWhere it showsGesture
Unreleased framesOn the canvas near your demoElement blur, reveal on cue
Client / project nameTab, breadcrumb, layers panelElement blur
Real user data in a mockupInside a dashboard designBox blur over the region
CommentsPins and threads on the canvasElement blur
Collaborator avatarsTop-right multiplayer clusterElement blur
What to hide in Figma and the gesture to use

Figma's canvas is a live web app that re-renders as you zoom and pan. BlurFirst stores a CSS selector for each blurred element and anchors box blurs to the page, so masks over the layers panel, the tab chrome and comment pins re-attach across re-renders. It stores the selector, never the design inside it, and everything stays local — nothing you blur leaves the browser and the only network request is a license check.

Two honest caveats. First, a box blur is anchored to the page, so it is best for fixed panels and static mockup regions; panning the canvas moves artwork beneath a fixed box, so use element blur for frames that live on the canvas. Second, BlurFirst covers the browser tab only — not the desktop app, other windows, or OS notifications — so open your file in the browser and mute notifications the usual way.

Frequently asked questions

Does BlurFirst work in the Figma desktop app?

No. BlurFirst is a browser extension, so it only works with Figma in the browser at figma.com. The desktop app is a native window that extensions cannot reach; open your file in the browser and share that tab instead.

Can I keep one frame visible while hiding the rest?

Yes. Element blur hides individual frames, and clicking a blurred frame reveals it, so you can walk through a prototype one screen at a time.

Will the blur show on Zoom or a Loom recording?

Yes. The blur is rendered into the page as real pixels before the screen is captured, so it appears on Zoom, Meet, Teams, Loom and OBS and on screenshots.

Does blurring a design upload it anywhere?

No. All blurring happens locally in your browser. Nothing you blur leaves the tab; the only network request the extension makes is a license check.

What about panning the canvas — does a region blur move with the art?

A box blur is anchored to the page, so panning moves artwork beneath it. For frames on the canvas use element blur, which follows the element; use box blur for fixed panels and mockup content areas.

Blur it before you share it.

Hide any field, region or message on a page before your next call. Nothing you blur leaves your browser.

Add to Chrome