Runway | BiRefNet v2 Adds Auto Background Removal to MCP
Runway introduced BiRefNet v2 background removal in MCP on October 15, 2026. It identifies the foreground automatically, preparing images for use in layouts and composites. For designers working through an agent, the useful change is bringing asset extraction closer to the conversation where the image's next use is being planned.
Prepare the foreground for its next composition
The integration is available on paid plans and is aimed at material such as product shots, illustrations and layout assets. Through MCP, the operation sits within a connected Runway workflow. Its value should be judged by the foreground it preserves and how that result behaves when placed into the intended design.
Choose a test image whose difficult areas are relevant to the project. Hair, thin handles, small gaps and pale edges can require different attention. Define which parts belong to the subject before evaluating the extraction. An apparently clean silhouette can still omit a small element that matters to the image's identity.
Inspect the boundary against more than one background
Place the extracted subject over both a light and a dark test background. Look for remaining fragments, missing edge detail and a visible fringe around the outline. Then compare it with the actual campaign background. These checks help identify where a quick extraction still needs normal image-editing work.
For a product asset, inspect the spaces inside the subject as well as its outer contour. Handles, straps and open frames need to read correctly after placement. Compare the result with the original photograph so an edge that looks tidy does not become the reason a distinctive detail disappears.
Treat placement and lighting as separate decisions
Removing a background does not decide where the subject should sit in the new layout. Review scale, crop and the space reserved for copy before finalizing the composition. A reusable product cutout can support several placements, but each one still needs a deliberate relationship between the subject and the text.
Compare the lighting of the extracted asset with the new environment. If the design needs a contact shadow or a different tonal balance, evaluate that as another editing step. Keep the extraction's quality separate from the success of the finished composite, so the review identifies the actual work still required.
Check access and retain the source image
Runway MCP uses the connected account's credits, with costs depending on the operation and settings. Confirm the available tool before preparing a batch. Keep the source image alongside the accepted extraction so another designer can compare details or make a different crop without having to recover the original later.
Before approving a set of assets, review them at the intended delivery size and in their actual placements. A small edge issue may be invisible in a thumbnail yet distracting in a large banner. Record which assets are ready to use and which need refinement, especially when several images share the same campaign.
Daisuki's Take: What This Means for Designers
We find the practical value in shortening the path from an image request to a usable foreground asset. The extraction still needs a visual acceptance check.
We would judge the boundary in context, then handle composition and lighting as their own decisions. That makes the review clearer and avoids approving a composite too early.
For designers, a reusable asset is one that survives the next layout. Keep the original reference and inspect the details that give the subject its recognizable shape.
Sources and Recommended Links
- BiRefNet v2 Background Removal - October 15, 2026 | Runway Official Changelog
- Runway MCP | Runway Official Product Page
