A split-screen preview shows two young men against a bright green background. The man on the left, wearing a black shirt, stands confidently. On the right, another man in a gray shirt holds a pink object and a drink while smiling. A circular inset displays a close-up of the first man.

Beeble adds CorridorKey green screen model

CorridorKey lands in Beeble Background Remover. Pick MatAnyone or CorridorKey before upload, then export RGBA or alpha for comps.

For those who don’t know the tool: Beeble Background Remover is a Cloud roto and matte extractor for comps, now offering CorridorKey or MatAnyone before upload, so your key tests can happen before your pipeline meeting turns into a sequel.

The interface of a video editing software, featuring a vibrant orange banner titled 'SWITCH', showcasing a smiling person next to the logo. Below are options to create content, including tools like 'Background Remover' and 'Beeble Editor', alongside recent creations displayed in square thumbnails with multiple copies of a man in a blue shirt against a green background.

What changed in Background Remover

Beeble‘s Background Remover now lets you choose between MatAnyone and CorridorKey before you upload footage. MatAnyone stays positioned as the general-purpose option. CorridorKey is positioned as the green screen option, aimed at cleaner edges and more accurate keying on chroma key shots. Background Remover runs only in the Cloud app and does not run in the desktop product.

The fastest way to try it without committing

CorridorKey has the kind of momentum that makes people want to try it immediately, and also the kind of setup that can make them postpone it indefinitely. If you do not want to download code, install dependencies, and explain to your producer why your machine is now compiling something called a model, running CorridorKey inside the Background Remover toolkit gives you a low-friction way to test it on your own footage first. That includes testing it against your current keys, and checking whether your exports land cleanly in your comp toolchain, without rebuilding that toolchain just to run an experiment.

How CorridorKey was invented

CorridorKey started as a response to a workload problem. A greenscreen-heavy show needed a lot of shots, and the team wanted an automated way to cut subjects out so they could spend time on the creative side of VFX instead of hand-cleaning keys frame after frame.

The design focus landed on a specific compositing headache: a greenscreen edge pixel often contains a mix of foreground and background light. A matte can be good and the color can still be wrong, because the plate already baked the screen contribution into semi-transparent detail. The CorridorKey approach targets a straight color foreground output paired with an alpha output, so semi-transparent materials, motion blur, and hair can keep behaving like actual transparency instead of looking like tinted cutouts.

Training data was coming from CG so the model could learn from mathematically clean answers. The workflow renders greenscreen plates, then renders the same foreground without the background and with a perfect alpha, giving the model ground truth for both color and transparency. Scale was coming from procedural variation, including procedural scene generation work in tools like Houdini and Blender to produce many variations in lighting, materials, objects, and motion without rebuilding each shot by hand.

Early results were treated as tests and iterated on through retraining. One tactic for pushing quality was to composite results over random backgrounds and neutral gray during testing, so leftover contamination becomes obvious and gets punished during training. The tool is being used as a first step in a broader pipeline, with outputs intended to drop into comp and realtime contexts in apps like Adobe After Effects and Unreal Engine.

What you get out of Beeble after a run

If you are testing CorridorKey for greenscreen work, this matters because the outputs determine how painful your handoff is. A quick trial that ends in a format conversion detour still counts as pain. It just wears a different hat.

Background Remover is built around alpha extraction for compositing and VFX workflows. You can upload a video, an image sequence, or a single image, then download results intended to slot into a comp.

On the Cloud pricing page, export options are listed as RGBA exports in MOV or PNG sequence and alpha exports in MP4 or PNG sequence. MOV here refers to the QuickTime container, PNG refers to the PNG format, and MP4 refers to the MPEG family container.

A close-up, round portrait of a person with a short, dark hairstyle, wearing a black shirt, looking attentively towards the camera. In the background, a darker interface displays options for video downloads, including RGB sequences, along with numerical information on frame rate and duration.

Pricing, credits, and practical limits

Background Remover usage is credit-based. The Cloud pricing is around image uploads as consuming one credit per image and video uploads as consuming one credit per second of video.

The plans listed include a free Starter tier that includes ninety credits per month and is labeled non-commercial. Two paid tiers have Background Remover included. “Creator” is listed at nineteen US dollars per month or sixteen US dollars per month when billed annually, with five hundred forty credits per month. “Professional” is listed at seventy-five US dollars per month or sixty US dollars per month when billed annually, with two thousand four hundred credits per month.

Per-upload maximums for video length are thirty seconds on the five hundred forty credit tier and one minute on the two thousand four hundred credit tier. There is also a batch upload up to twenty files at once on the paid tiers.

A production reality check

CorridorKey is a model option, not a replacement for judgement. Every keying tool behaves differently across compression, sensor noise, spill, lens artifacts, and the very special chaos of talent wardrobe choices. Test CorridorKey on your own porudction plates before you trust it with a deadline, and keep your existing approach ready for the shots that refuse to behave.

If the results look good, treat the first integration step as a controlled experiment: run a small batch, validate edge stability, validate color behavior in the semi-transparent areas, validate the exports in your comp, then scale up. That is less romantic than a revolution, but it is how tools earn their place in compositnig pipelines.


https://docs.beeble.ai/beeble/background-remover

https://github.com/nikopueringer/CorridorKey

https://beeble.ai