Stop treating an old tutorial's menu as the current product
A merchant following an older Runway product-video tutorial may search for All Tools, Magic Tools, Remove background, or Motion Tracking. When those controls are absent, repeating the tutorial's navigation steps will not resolve the problem.
Start by identifying the exact operation the tutorial intended. Background removal isolates a subject from its surroundings. Motion tracking estimates the movement of a visual feature so another element can follow it. These tasks may appear together in a product advertisement, but they are not substitutes.
Runway's current deprecation table lists Video Backdrop as the replacement for the old Remove background tool and N/A for Motion Tracking. The retired All Tools page should not be treated as an available navigation destination.
Route the task, not the old button name
Video Backdrop is Runway's listed alternative for the retired Remove background tool. That listing does not promise identical masking behavior, alpha export or every legacy control. Verify the current output needed by the job.
For a product clip that needs a different background, investigate the currently documented Video Backdrop app and its actual capabilities. Confirm that the task is background replacement rather than merely adding a solid-colored rectangle behind a product.
For a moving feature label, do not assume Video Backdrop provides the retired motion-tracking behavior. Identify whether the intended deliverable needs a tracked point, a stable attachment offset, or an annotation that follows a rotating product. Those requirements belong to a tracking and compositing workflow.
If the old tutorial also relied on foreground masks, shadows, or object removal, separate those responsibilities before choosing tools. A background change does not automatically provide tracking data, and a tracked annotation does not automatically separate foreground objects.
Illustrative case: a moving coffee grinder
Choosing an external tracking-capable editor is an editorial handoff recommendation. The official N/A entry only establishes that this table lists no direct replacement; it does not prohibit external tracking.
A fictional seller has a short video of a coffee grinder rotating on a tabletop. The production brief requires a clean studio background and a label that follows the grinder's power switch.
An old Runway tutorial instructs the editor to remove the background and then apply Motion Tracking from All Tools. The current migration decision has two branches.
| Required result | Current route to investigate | Exit condition |
|---|---|---|
| Replace the original background | Runway Video Backdrop | Background candidate reviewed |
| Keep the switch label attached during rotation | Separate tracking-capable editor | Label attachment reviewed across the shot |
| Make the label pass behind a hand | Tracking plus foreground masking and compositing | Correct overlap at the crossing |
This is a hypothetical routing exercise. No Runway app or external editor was operated.
Use the existing mechanism-specific guides
For label attachment, the existing moving-product callout guide explains tracking features and attachment offsets. For a label passing behind a hand, the tracked-label occlusion guide covers foreground masking and compositing order.
Those procedures are not Runway replacements supplied by CartVisual. They are separate external editing tasks. The absence of a direct replacement in Runway's table should lead to a workflow choice, not an invented hidden Runway control.
Retire the obsolete production instruction
Update the internal tutorial or task brief to identify the retired command, its documented status, and the replacement route where one exists. Remove screenshots that instruct colleagues to open the deleted All Tools page.
Keep the original clip, the intended background treatment, the tracking requirement, and the final output as distinct records. If an external tracking project is used, preserve its editable project file separately from the exported video.
Exit the migration task when every old tutorial step has a current, verified owner or is explicitly marked unsupported. Do not describe a missing Runway feature as restored merely because a visually similar result can be created elsewhere.