Screenshots preset · checkerboard · WebP · UI Erase tip
Background remover for UI screenshots and app windows
Product docs and release notes: transparent checkers for window edges, Erase desktop icons carefully, WebP for lightweight help centers.
✦ AI Powered🔒 100% Private⚡ Instant📐 HD Export
Drop your image here
or click to browse · paste with Ctrl+V Supports all major image formats
JPGPNGWebPGIFBMPTIFFAVIFHEICSVGICO
Removing background
Initializing AI model…
0%
Detecting acceleration…
⚠️
Processing failed.
100%
Brush
Size30
Opacity85%
Hardness70%
Background
Export
Shortcuts
Smart eraseS
Hard eraseE
RestoreR
Pan toggleP
Zoom toolZ
Zoom in/out+ / -
Scroll zoomWheel
Fit view0
Pan (hold)Space
Undo / RedoCtrl+Z
Brush size[ ]
Product UI docs
UI window cutouts without uploading product screens
Product marketers and docs writers need clean app windows extracted from messy desktops without sending proprietary UI to a cloud remover. This preset starts on transparent checkers so window chrome and shadow decisions stay honest, suggests Refine for soft OS shadows when desired, and highlights WebP for lightweight help centers and changelogs. Security teams appreciate that unreleased admin panels never transit a third-party API during cutout. Use transparent-png when lossless design-system archival is the priority; use screenshots when docs delivery weight matters.
Why this preset
Why UI screenshots gets this locked preview
Checkerboard proves you have real alpha around the window, not a cropped JPG with leftover wallpaper. Suggest Refine helps when you want a slightly softer OS shadow lip, while Smart Erase remains the main tool for desktop icons. WebP keeps documentation sites fast. The tip tells authors to erase icons while preserving window chrome — the classic screenshot failure mode.
Capture at 1x or 2x deliberately. Import, erase desktop icons and wallpaper gaps, Refine once only if you want a softer outer lip, export WebP for docs or PNG for design critique. Avoid capturing secret data in the screenshot itself. Prefer built-in OS window shadows only when brand guidelines allow them; otherwise Erase to a hard chrome edge.
Scenario
Changelog and help-center batches from staging builds
Open this preset when a release needs twenty clean UI figures. Capture staging windows carefully, cut on checkers, erase desktop clutter, export WebP into the docs repo, and keep PNG for the design critique thread. If a figure includes customer data, redact before cutout. For dark-mode UI, flip to a light proof swatch briefly to ensure chrome edges are not missing. Consistency in scale across figures matters more than perfect soft shadows.
Edge craft
Window chrome, OS shadows, and desktop icon crumbs
Screenshot edges fail when wallpaper peeks along rounded corners or when icons leave crumbs. On checkers, zoom every corner radius. Smart Erase icons and menu bar junk. Decide whether the OS shadow stays; if it stays, Refine gently once for a clean lip; if not, Erase to the hard chrome. Avoid Refine on crisp UI text inside the window — you are editing the outer matte, not the pixels of the product. Export WebP when the window reads clean at article width.
Privacy by architecture
On-device cutouts for UI screenshots
UI screenshots can expose customer names, API keys, and unreleased features. Local cutouts stop an entire class of accidental SaaS uploads during the cleanup stage. Still redact sensitive strings in the original capture before you share exports. Treat help-center images as production data under your normal DLP rules.
Preset FAQ
FAQ — UI screenshots background removal
Should documentation figures keep the OS shadow?
Follow brand guidelines. Soft shadows can look native but also pick up wallpaper color. Many design systems prefer a hard window edge plus a synthetic shadow in Figma. This preset lets you QA either choice on checkers.
Why WebP instead of PNG for screenshots?
Help centers load many figures. WebP reduces weight. Keep PNG when designers will zoom into chrome for critique or when lossless archival matters. Re-export from the same matte as needed.
Can I cut a multi-window composition at once?
You can, but overlapping windows are harder. Cutting each window separately and compositing usually looks cleaner for tutorials. Keep scale consistent across the set.
How do I avoid leaking PII in UI captures?
Redact in the staging data or blur before capture when possible. Cutout does not remove text inside the window. Local processing only prevents uploading the image to a remover — it does not scrub content.
Do rounded macOS corners need special care?
Yes. Zoom each corner and Erase wallpaper wedges. A one-pixel wallpaper sliver becomes obvious on light article backgrounds. Checkers make those wedges easier to see than a white proof.
I keep this page because background removal for Screenshots kept failing with upload tools or generic presets. Here you run the local cutout, Refine hair/edges, export PNG or white JPG as the channel requires. Limits and architecture are documented in Lab Notes — this URL is a micro-instrument for one job, not a keyword clone.
