Trusted by 2000+ users.

Capture the web, polish in the editor, ship effortlessly.

Highlights, blur, arrows, layers—and Copy to Figma when your file needs the frame. Capture, annotate, and ship—without breaking your flow.

Figscreen Chrome extension open on the Capture tab.

Trusted by 2000+ users.

Capture screens, add context, and hand off faster—all from one Chrome extension.

Figscreen Chrome extension onboarding.

Connect once—same wallet in Chrome and Figma

Activate with your app key or Google and tie the popup to your Figscreen credits. One balance powers capture and your community plugin.

Viewport, full page, or draw an area

Choose how much of the page to grab in seconds. Area capture uses a fast region select—built for shipping screenshots, not fighting the browser.

Figscreen Capture tab.
History with captures.

History that stays out of your way

Jump back to recent captures or copy URLs from a simple list—without hunting through folders.

Credits & plan in Settings

See what’s active, rotate keys, sign out, or report an issue—without leaving the popup.

Settings tab.

Seamless integrations with your entire tech stack

Messy captures to clean Figma frames

Problems on the left converge through Figscreen, then ship as outcomes on the right — same layout as your day-to-day handoff.

Diagram: messy captures through Figscreen to clean Figma frames.

What our beta users shared with us

Honest notes from product designers, design leads, researchers, and engineers using Figscreen across Chrome and Figma.

The editor is where Figscreen clicks for us—highlights, blur, arrows, and layers, then straight into the deck.

When stakeholders ask for pixels, we’re already there.

James Liu
Product designer

I live in the Chrome popup for quick captures.

Viewport vs full page is one click—the Capture tab is fast enough that I don’t reach for anything else.

Michael Reyes
Design lead

Finally one tool for capture → annotate → ship.

Copy to Figma is the bridge we were missing.

Nina Deshmukh
UX researcher

Credits match everywhere.

I don’t think about whether I’m in the extension or the plugin.

Alina Kim
Founder

We had the team capturing in under five minutes—no workshop required.

Batch URLs in Figma for design QA audits is a huge win.

Sam Carter
Engineering manager

We use Figscreen for competitor teardowns: capture, redact, annotate, export.

The workflow replaced three tools.

Taylor Park
Product marketing

Blur for PII before sharing in Slack is non‑negotiable.

Doing it in-browser saves so much time.

Riley Voss
Security-minded PM

Our interns figured out full-page capture and the editor without a Loom.

That rarely happens with design tools.

Elena Mora
Design ops

Handoff used to mean screenshots in a folder and lost context.

Now it’s one annotated frame with arrows—PMs actually read it.

Jordan Webb
Frontend engineer

One wallet for Chrome and Figma.

Two products, one credit balance. Whatever you buy below works across the Chrome extension and the Figma plugin — same account, same credits, no double-paying.

Pay as you go

Starter Pack

Perfect for occasional use—buy credits once, use them anytime.

50 credits

$5 one-time

Get started

What’s included

  • 1 credit = 1 screenshot
  • 1080p HD quality
  • Desktop + Mobile views
  • Credits never expire
  • Use anytime, no subscription
Popular

Power Pack

Best value for regular creators who capture and annotate every week.

120 credits

$9 one-time

Get started

Everything in Starter Pack, plus:

  • 1 credit = 1 screenshot
  • 1080p HD quality
  • Desktop + Mobile views
  • Credits never expire
  • Use anytime, no subscription
  • Batch up to 25 URLs Figma

FAQs

Quick answers about captures, credits, the Figma plugin, exports, and billing — so you can get back to designing.

What is Figscreen?
Figscreen is a Chrome extension built around capture and a full annotation editor—highlights, blur, arrows, layers, and more—with optional Copy to Figma when your file needs the frame. The Figma Community plugin adds bulk URL import on the canvas. One account and shared credits across both.
How do I get started?
Install from the Chrome Web Store, then sign in with Google or activate with your app key. Add the Figma plugin from Community when you want batch URL imports directly on the canvas.
What capture modes are available in Chrome?
From the Capture tab you can grab the viewport, a full-page scroll capture, or draw a region on the live tab. Everything opens in the editor so you can annotate before exporting or copying to Figma.
How do credits work across Chrome and Figma?
Credits live on your Figscreen account and apply whether you’re capturing in Chrome or running batches in the Figma plugin. Usage depends on the actions you run; you can see what’s active and manage billing from the app. Compare packs and plans on Pricing.
What does Copy to Figma do?
When your canvas needs the frame, Copy to Figma sends your annotated capture from the extension into a Figma file so you can keep designing—not another static screenshot lost in a folder.
Where does bulk URL import run?
Only in the Figma plugin—paste up to 25 URLs per batch, use device presets, and drop full-page frames. In Chrome you always capture the live tab (viewport, full page, or region).
Can I blur or hide sensitive content before sharing?
Yes. The editor includes blur and other annotation tools so you can redact PII or messy UI before you export, copy to Figma, or hand off to teammates.
What can I export from the editor?
You can export your annotated captures in common image formats for decks, docs, tickets, or Slack—exact options appear in the extension UI. Copy to Figma is there when you want a live frame instead of a flat file.
Is there a free tier?
Yes. A limited free tier lets you try the workflow before upgrading. When you’re ready, choose a credit pack or monthly plan on Pricing.
How do I change or cancel my plan?
Manage subscription and payment methods from your Figscreen account in the web app. If you need a hand, use Share feedback or Report a bug from the site footer.
Does Figscreen work in browsers other than Chrome?
The capture and editor experience is built as a Chrome extension today. Chromium-based browsers that support the Chrome Web Store may work, but we optimize and test for Google Chrome.
From the founder

Why I built Figscreen.

A few years ago, I was spending more time managing screenshots than actually designing.

Every project meant too many tabs open, messy crops, blurry annotations, and dragging screenshots into Figma one by one. The most frustrating part was importing dozens of website screens onto a canvas manually — it felt like pure busywork.

So I built Figscreen.

It started as a Figma plugin that could capture and import website screenshots directly into Figma in bulk. I launched it on Product Hunt in May 2025. It only got 19 upvotes, which honestly felt disappointing at the time. But the people who used it kept coming back, and one request kept showing up again and again:

“Can I capture and annotate before sending it to Figma?”

That question turned into the Chrome extension.

Using AI, Figma, and WordPress, I designed it, built it, wrote everything, and figured things out along the way. Before it ever made it to the Chrome Web Store, it got rejected three different times. Each rejection meant going back, fixing issues, rewriting parts, and resubmitting again.

Then finally — on 5/9/2026 — it went live.

Today, 2,000+ designers use Figscreen every week across Chrome and Figma together. Clean captures, proper annotations, and one-click export into Figma without breaking the workflow.

If screenshots are still slowing down your design process, give it a try. You can start without a card.