Crop GIF on Windows

Your screen recording GIF shows the full 1920 px desktop, but the bug lives in a 600 px panel on the left. Cropping to that panel can cut file size more than lowering fps alone. GIF size grows with pixel count: fewer pixels per frame means fewer bytes in every frame of the loop. Cropping locally keeps unreleased product UI off random upload sites. Windows QA teams that capture full-screen repros daily benefit from a consistent crop preset instead of re-measuring coordinates in PowerShell every ticket.

Why crop GIFs before sharing

Full-screen GIF captures include taskbar icons, empty space, and background apps that do not help the reader. Cropping focuses attention on the interaction and reduces width and height simultaneously.

Factor	Effect on GIF size
Width	Quadratic feel (half width often cuts size sharply)
Height	Same as width; tall captures hurt
Dead space	Wasted palette budget on static pixels
Duration	Unchanged by crop, but smaller frames help

Crop before compression, not after. Re-palette encoding on an already compressed GIF adds generation loss. See compress GIFs on Windows for palette tuning after you crop.

Capture habit	Better approach
Full-screen 1080p repro	Crop to app window, then compress
Window recording	Crop to control or button area
Multi-monitor setup	Crop to single display region

When the source is still video, trim and crop in Clipchamp first, then export MP4 if the tool allows video. See video to GIF on Windows when you must ship GIF. See lossy vs lossless compression when you wonder why repeated GIF re-encodes look muddy.

Choose crop dimensions

Pick a crop box that includes the UI element plus a small margin for context. Bug reports need enough chrome to show which screen or modal failed; marketing loops need tighter framing.

Use case	Margin around action
Bug repro	20 to 40 px padding
Feature demo	40 to 80 px padding
Icon or button focus	Tight crop, 10 px padding

Measure crop coordinates from the top-left corner of the GIF: crop=width:height:x:y.

Example: a 1920×1080 GIF with action in the left 700×500 region starting at (80, 120):

crop=700:500:80:120

Odd width or height values can cause issues with some codecs. Use even numbers when FFmpeg warns about chroma subsampling.

Common mistake	Fix
Crop cuts off tooltip	Expand height by 40 px
Crop includes taskbar	Move y offset up
Text unreadable after crop	Widen crop or scale after crop

Preview one frame in Photos or GetCompress before batch cropping ten files from a test pass.

Crop GIF with FFmpeg

Install FFmpeg with winget:

winget install --id Gyan.FFmpeg -e

Crop and re-encode with palette pipeline:

ffmpeg -i full-screen.gif -vf "crop=700:500:80:120,fps=10,scale=700:-1:flags=lanczos,split[s0][s1];[s0]palettegen[p];[s1][p]paletteuse" -loop 0 cropped.gif

Crop only, no re-palette (faster, may keep original palette quirks):

ffmpeg -i full-screen.gif -vf "crop=700:500:80:120" -loop 0 cropped-raw.gif

Batch crop when every file shares the same capture layout:

mkdir cropped-out
Get-ChildItem *.gif | ForEach-Object {
  ffmpeg -i $_.Name -vf "crop=700:500:80:120,fps=10,split[s0][s1];[s0]palettegen[p];[s1][p]paletteuse" -loop 0 "cropped-out\$($_.Name)"
}

Step order	Why
Crop first	Smaller frames for palettegen
Then fps / scale	Further size control
palettegen last	Tuned to cropped content

Keep originals until cropped output passes review in the target ticket system.

Measure crop coordinates from a screenshot opened in Paint or your design tool when ffplay is not installed. Note x and y from the top-left of the image, then plug values into the FFmpeg filter string.

Using GetCompress

GetCompress fits crop GIF on Windows when you want visual crop handles, frame preview, and export without measuring coordinates in PowerShell.

Drop an existing GIF or source MOV/MP4 to crop before palette export.

Workflow features that help:

• Preview and trim: cut idle seconds before you crop dead pixels.
• Frame preview: verify tooltips and labels survive the crop box.
• Visual crop: drag edges instead of guessing x and y offsets.
• Width presets after crop: 640 or 800 px for upload forms.
• Switch to MP4: export video when the thread allows it after crop.
• Local processing: keep staging UI off online converters.

Save a preset like “QA crop 700w 10fps” when your app window size is stable across builds. When the crop box varies per bug, still trim first: three seconds of focused UI beats ten seconds of full desktop at any resolution.

GetCompress also helps when design sends full-canvas GIF exports from Principle that include artboard padding. Crop to the component, compare against MP4 export in the same window, and attach the smaller format the thread accepts.

Batch queue ten full-screen repros after a regression pass, apply the same crop region when layout is fixed, and export GIF or MP4 with one preset instead of maintaining separate PowerShell scripts per engineer.

Clipchamp trim plus GetCompress crop covers most Windows QA workflows without installing FFmpeg on every laptop. Keep one shared preset screenshot in the team wiki so contractors match in-house crop settings on day one.