Drop a video or image here
or choose a file · or paste a URL below
MP4 · WebM · MOV · PNG · JPG · WebP · GIF · BMP
Key colour
Chroma key
Background
Output
How to remove a green screen from a video or photo
- Load the clip. Drag an MP4, WebM or MOV onto the box above, or drop a PNG / JPG if you only need a still. Everything happens on this page — the file is never uploaded to a server.
- Pick the key colour. Use the eyedropper button and click the green in the preview, or hit one of the presets. Studio green is
#00B140; blue screens are usually#0047BB. - Raise Tolerance until the background goes. Stop as soon as the last patch of green disappears. Going further starts eating the subject.
- Add Edge softness. 10–20 is usually enough. This is what keeps hair and motion-blurred edges from looking like they were cut with scissors.
- Raise Spill suppression. If you can see a green rim on shoulders or hair, push this until the rim goes neutral. 30–50 covers most footage.
- Choose the background. Transparent for a later edit, a colour if you are publishing straight away, or your own image.
- Trim the clip. Drag the two handles in the Clip bar if you only need a few seconds — rendering 6 seconds instead of 60 is roughly ten times faster.
- Render, then download. MOV, MKV and APNG keep transparency in video. PNG and WebP keep it in a still. MP4 and GIF cannot store alpha, so they always need a colour or image background.
Supported formats and limits
Input
| Type | Formats | Read via |
|---|---|---|
| Video | MP4, WebM, MOV, M4V, AVI, MKV (whatever your browser can decode) | Direct file or URL |
| Image | PNG, JPG, WebP, GIF (first frame), BMP | Direct file or URL |
Output
The Alpha column is measured, not assumed: every "Yes" below was checked by encoding a half-transparent frame, decoding it back and reading the alpha value. The transparent half came back at 0.
| Format | Alpha | Best for |
|---|---|---|
| PNG | Yes | Stills to drop into a design file |
| WebP | Yes | Smaller stills for the web |
| MOV (QuickTime Animation) | Yes | Transparent video for a desktop editor. Large files. |
| MKV (FFV1) | Yes | Transparent video, mathematically lossless. Very large files. |
| APNG | Yes | Short transparent loops that play anywhere without a plugin |
| GIF | No | Short opaque loops; 256 colours, so expect banding on gradients |
| MP4 (H.264) | No | Social uploads — needs a background colour or image |
Transparent WebM (VP9 with an alpha plane) is deliberately absent. It looks supported — ffmpeg accepts -pix_fmt yuva420p and reports the stream as yuva420p — but the alpha plane does not reach the output. Measured here on ffmpeg.wasm 0.12.10 (ffmpeg 5.1.4) and on a desktop ffmpeg 9.0.1: both write a file that decodes back as yuv420p, meaning a background would silently reappear. Rather than ship a file that lies about its transparency, the option is not offered.
Unit conversion: file size and render time
Bitrate is what governs size for the lossy formats. The arithmetic below is the standard video bitrate formula, so you can run it on your own numbers.
| Quality | Bitrate (1080p) | 10 s at 30 fps | Formula |
|---|---|---|---|
| 480p, web preview | ~1.0 Mbps | ~1.25 MB | MB = Mbps × seconds ÷ 8 e.g. 5 Mbps × 10 s ÷ 8 = 6.25 MB |
| 720p | ~2.5 Mbps | ~3.1 MB | |
| 1080p, quality 70 | ~5 Mbps | ~6.25 MB | |
| 1080p, quality 100 | ~8 Mbps | ~10 MB |
Source of the bitrate column: the encoders' own default targets, not measurements of your footage. Real files land within roughly ±20% depending on how much motion is in the frame. This table applies to MP4 and GIF only — the three alpha formats store raw frames and ignore the Quality slider entirely.
Unit conversion: what an alpha video costs
Alpha formats cannot be compressed the way MP4 is, because every pixel has to survive exactly. Size is simply frames × pixels × bytes per pixel.
| Format | Bytes per pixel | 10 s at 30 fps, 1080p | Formula |
|---|---|---|---|
| MOV (qtrle) | ~2.2 | ~2.1 GB | GB = frames × W × H × bpp ÷ 1024³ 300 × 1920 × 1080 × 2.2 = 1.37e9 B = 1.27 GiB |
| MKV (FFV1) | ~3.0 | ~2.9 GB | |
| APNG | ~1.6 | ~1.5 GB |
Source of the bytes-per-pixel figures: 4 bytes per pixel is the raw RGBA size; the divisors are the measured compression this build achieved on a flat-subject test clip. Treat them as planning estimates, not guarantees — busy footage compresses worse. The tool refuses a render it estimates above 1.6 GB rather than letting the tab die.
Unit conversion: render time
Keying costs roughly the same per frame regardless of which machine you use, so a two-times increase in frame count is a two-times increase in wait.
| Clip | Frames | Relative wait | Formula |
|---|---|---|---|
| 5 s @ 24 fps | 120 | 1× | frames = seconds × fps relative wait = frames ÷ 120 |
| 10 s @ 30 fps | 300 | 2.5× | |
| 30 s @ 30 fps | 900 | 7.5× | |
| 60 s @ 60 fps | 3600 | 30× |
Source: computed from the frame counts above. No wall-clock measurement is claimed here, because speed varies by machine and is not something this page can promise.
What this tool cannot do
Being explicit about the limits saves you a wasted afternoon.
- One file at a time. There is no batch queue and no multi-file drop. Queue of 12 clips means 12 passes.
- No account, so no history. Nothing is stored. Refresh the tab and the clip is gone; export before you reload.
- No API. Everything runs inside this tab, so there is nothing to call from a script.
- No manual matte painting. You get global sliders, not a per-frame rotoscope brush. Badly lit footage with a wrinkled screen will still need a desktop compositor.
- Shared-memory limits. Long clips at 4K can run the tab out of memory. The Clip bar exists for this — trim first, then render.
- MP4 and GIF lose transparency. That is the container, not the tool. For transparent video use MOV, MKV or APNG.
- Mobile browsers. The controls work on a phone and nothing overflows, but a long video render on a phone is slow and may be killed by the OS when you switch apps. Keep renders short on mobile.
Last reviewed: 17 September 2026.
Frequently asked questions
Is this the same as a chroma key background remover?
Yes. Green screen removal, chroma key, chroma key background remover and green screen background remover all describe the same operation: one flat colour is made transparent and everything else is kept. This page handles all of those phrasings with one set of controls — there is no reason to split them across separate pages.
Can I remove the green screen from a video, not just a photo?
Yes. Load an MP4, WebM or MOV and the same sliders apply to every frame. Export as MOV, MKV or APNG if you need the transparency to survive the render; MP4 and GIF will ask you for a background colour or image first.
How do I get a clean edge on hair?
Two sliders, in this order. Raise Tolerance only until the background is gone, then use Edge softness to bring back a natural transition. If a green fringe remains on the hair, raise Spill suppression until it turns neutral. The most common mistake is pushing Tolerance too high — it never fixes hair, it just eats the subject.
What is the best key colour for a green screen?
Digital chroma green #00B140 is the broadcast standard and the preset here. Blue #0047BB is the alternative when the subject is wearing green. Black and white work as keys too when the scene genuinely has a flat black or white backdrop, though you will need a tighter Tolerance.
Does a spill suppression slider make the subject look grey?
Only if you overdo it. Spill suppression is a green-channel limiter: it pulls down green where green is stronger than red and blue, which is exactly what a light bounce off the screen looks like. Skin rarely trips it. If the whole subject looks desaturated, take it back down rather than compensating elsewhere.
What does AI subject mode change?
Instead of keying a colour, it segments the person from the frame. That is the right choice when the background is not a flat colour at all — an office, a street, a messy room — or when the green screen is unevenly lit. It is slower than pure colour keying, and it can still miss a raised hand or a wisp of hair, so check the result before exporting.
Is my video uploaded anywhere?
No. There is no upload step and no server-side processing. The file is read by your own browser and the frames are keyed on your own device. You can watch the network tab stay quiet while it works, or turn off your Wi-Fi and run it — it will still render.
Why does a 60-second 4K clip take so long?
Every frame is decoded, keyed and re-encoded inside one browser tab. A 60-second clip at 60 fps is 3,600 frames, so it costs roughly 30 times the wait of a 5-second clip at 24 fps. Trim with the Clip bar first — cutting to the six seconds you actually need removes about 90% of the work. Note that the alpha formats store raw frames, so a long clip also eats disk when you download it.
Does it work on a phone?
The layout drops to a single column below 720 px, the controls are touch-sized and results never overflow the screen. Short clips export fine. Long clips are a bad idea on mobile: the tab gets suspended when you switch apps and the render dies.