Guides

All Guides

Short answer: every guide on this site, grouped by the problem you are actually stuck on rather than by the order they were written. If the cut-out looks wrong, start with the first group. If the result looks right but the file is wrong, jump to the third. The tool itself needs none of this — open the green screen remover and drop a photo in.

When the cut-out looks wrong

Why the edge looks wrong — a symptom-by-symptom table: hard outline, pale halo, chewed edge, holes inside the subject, and which control fixes each one.
How the key decides — the single per-pixel question behind every slider, and the three consequences you can predict from it.
Photos are judged harder than a frame — why a still is inspected at 100% when a video frame is not, and what that changes about your settings.

Choosing the key colour

Choosing the key colour — where to sample, when to switch to a blue screen, and why a green subject inverts the usual advice.
When a key cannot work — the four failure patterns, including spill, motion blur and subjects that carry the screen’s own colour, plus a 60-second check.
When the subject is white too — white on white has no colour difference to measure, so no slider position can separate it. The five-second test, the contact-shadow method, and the shoot-side fixes that end the problem for good.
When green is not a screen — a painted wall, a hedge and a folded cloth with the same hue and three different outcomes, plus the ten-second test that tells you which one you have.
Three starting points — a solid colour, a flat studio sweep, or a scene. Two of them are colour jobs and differ only in which colour you name; the third needs a different method entirely.
When the subject is see-through too — glass, chiffon, smoke and soft shadows need a fraction of the background kept, not a decision between keeping and deleting it. Why no slider position reaches that, and the four routes that do.

Getting the file out intact

Formats that keep transparency — what transparency actually is in a file, and why a transparent export sometimes comes back sitting in a white box.
Three decisions the export freezes — what you are actually holding after the removal, and the three choices that stop being adjustable the moment you export.
Reading the file you already have — three different files get called a transparent-background PNG and only one of them is one. The ten-second dark-background test, and why one-bit alpha comes out jagged.
Start empty, or remove what is there — the one word that hides two different jobs, why new-file dialogs quietly give you an opaque white canvas, and the four ways a transparency you created gets destroyed on the way out.
When there is nothing left to remove — if the PNG is already cut out, running a remover over it again cannot help and deletes the blended edge pixels that made the outline look right. The five-second test, and the rule about re-cutting from the original.
Where the transparency comes from — a colour decision, a drawn shape, or an image that already carries it. Each fails in its own way, and the one trap that only appears when you combine them: stacked alpha multiplies.
When the background is paper — text, a signature, a chart or line art on white needs brightness turned into alpha, not a colour removal. Why keying white leaves halos or eats thin strokes, and how the tone-based route avoids the choice.
The canvas is still there — removing a background removes colour, not area. Why a perfect cut-out still lands off-centre, looks small after resizing, or shifts everything when it replaces an older file.
The handover check — the phrase names four properties at once: container, alpha, edge and canvas. Seven checks, in the order that catches the failure each one produces.
Three kinds of edge — a logo is a shape edge, a blended band and often a shadow. Why a global white removal punches holes in the counters and leaves a ring no tolerance can fix, and the order of files to try before keying anything.
Fix the white first — a photographed white runs from 255 to 214, and a tolerance wide enough for the dark corner eats the subject. Measure the spread, raise the white point, then key once.
The frame is the unit — a video is thousands of stills, so a key only counts if it holds on the worst frame and stays stable across the shot. Which frame to test, why a fixed threshold drifts, and why flicker reads worse than a soft edge.
Which background — the phrase names two things: the screen behind the subject and the scene you want instead. Key first, clean the edge and spill, then composite; swapping that order is what makes a cut-out look pasted on.
Without a green screen — with no screen there is no colour to key, so the software guesses what the subject is in every frame. What that breaks (hair, occlusion, stability) and when a screen is still the cheaper answer.
Order of operations — in Premiere the sliders are the easy part. Garbage matte before the key, key before the grade, and a still-frame test before either; why moving the grade changes the matte.
Remove background from video — every video background remover uses one of three masks: a colour you chose, a model’s guess, or a shape you drew. Which one the footage allows, and the four decisions the export freezes.
Background remover PNG — with a PNG input the colour type and bit depth set the ceiling before any slider moves. Palette PNGs cannot hold a soft edge, screenshots carry the checkerboard as pixels, and lossless storage is why PNG beats JPEG here.
No background — the phrase covers a transparent PNG, an opaque photo on seamless white, and video with a replaced scene. Which one is being asked for, the marketplace trap, and the ten-second test.
AI background remover — the model gets the mask by guessing instead of measuring. What that wins (no screen needed), what it costs (hair, glass, certainty), and why most AI tools upload while a colour key does not.
Background eraser — an eraser writes transparency where you brush; a key applies one rule everywhere. Why repeated strokes compound, how to spot an eraser that is really a key, and when hand work is the only route.
Bg remover: pick the method — sample three points on the background before choosing a tool. Three values that match mean a colour key; a wide spread means a model or a hand mask.

What happens after the removal

Replacing the background — the six tells of a pasted-on composite, and the one-step fix for each.

Working with more than one image

Keeping a batch consistent — which three settings have to stay fixed across forty files, which one must vary, and how to record the batch so it can be re-run.

The shortest route, start to finish

Remove green screen from a photo — three steps from one photo to a usable transparent PNG, with the first thing to check at each step when it goes wrong instead of the last.

Choosing the tool

What you are actually replacing — three routes through the same job, ranked by what you still need to do afterwards rather than by feature count.
Where your photo actually goes — the one decisive test for telling a browser tool from a server-side one, the four weaker signals, and what each result proves.
What free should mean — the four separate promises behind the word, and a thirty-second test for any tool.
Two jobs behind one phrase — why “removing a green screen” in an editor can mean two different operations that fail in opposite ways.

Where to start if you only read one

If the removal is going wrong and you do not know why yet, read the edge guide: it is written as a lookup table, so you can find your symptom and stop. If the removal is fine but the tool choice is the open question, read what you are replacing. Everything else is depth on one of those two.

Open the green screen remover — free, no account, runs in your browser, and your photo never leaves your device.