Adobe Removes Objects From 10-Second Videos Right on the Premiere Pro Timeline

Adobe has added a Generative Remove tool to Premiere Pro Beta: the editor selects an unwanted object with a mask, a tracker follows it frame by frame, and Firefly fills in the background. It all happens right on the timeline, so there is no longer any need to move a scene to After Effects just to remove a microphone in the corner or a random passerby. For video teams this speeds up minor cleanup, but for now it only suits short clips.

AI-processed from TG: @cgevent (Метаверсище и ИИще); edited by Hamidun News
Adobe Removes Objects From 10-Second Videos Right on the Premiere Pro Timeline
Source: TG: @cgevent (Метаверсище и ИИще). Collage: Hamidun News.
Listen to article
Article Fact Sheet & Key Figures
ParameterDetails
Primary sourceTG: @cgevent (Метаверсище и ИИще) ↗
Editor-in-Chief
Key metric #1The beta processes clips of up to 10 seconds, from 480p to 1080p SDR.
Key metric #2H.264 and HEVC are supported at no more than 30 frames per second.
Key metric #3Each generation attempt consumes Adobe Firefly credits.

A microphone crept into the edge of the frame, a person walked behind the subject, and someone else's logo remained on the wall. Previously, this kind of cleanup often meant a separate composite in After Effects, manual tracking or an export to a third-party service. Adobe is moving this work directly into Premiere Pro: the beta now includes Generative Remove, which deletes a selected object and restores the background in its place.

In a simple example, the process looks like this. The editor opens a clip in the Program Monitor, outlines a lighting stand using Object Mask or a vector shape, and captures its shadow along with it. The built-in tracker follows the selected area throughout the clip. After the editor clicks Remove, the cloud-based Firefly model analyzes neighboring frames and fills in a consistent background.

For video creators, this is not new magic but a shortening of a familiar production chain. The main change is not generative removal itself, but the fact that masking, tracking, generation and review of the result are now all gathered inside the editing timeline.

What Changes in the Workflow

Processing runs in the background and should not block further editing or playback of the project. The result remains non-destructive: Premiere marks the processed clip with a special AI badge. Through it, you can repeat the generation, adjust the mask boundaries or return to the original footage.

This is especially useful for small fixes that used to be too noticeable to ignore but too minor to justify a full round of compositing. For example, in a ten-second product video you can remove the edge of a microphone, a reflection of the film crew or a passerby in the background without leaving the main project.

Several objects can be removed at once by creating a separate mask for each. However, quality still depends on the scene. If an object covers a face, a complex texture or most of a moving background, the model will have to reconstruct information that may not exist in the frames. In such cases, manual review of every section remains mandatory.

Beta Limitations

Currently, Generative Remove works only with clips up to 10 seconds long. Resolutions from 480p to 1080p SDR are supported, at no more than 30 frames per second. The declared codecs are H.264 and HEVC. Adobe promises to add HDR and 10-bit color later.

There is also an economic limitation: each generation consumes Adobe Firefly credits. Teams that want to build the feature into a regular production flow should take this into account. A failed mask, a repeat variation or several objects to remove turn cleanup from a one-off operation into a measurable cost item. Until stable pricing arrives, it makes sense to compare the cost of generations with the time of an editor or compositing specialist.

Cloud processing adds two more questions: the upload speed of source files and the rules for handling confidential material. If a team is editing unreleased advertising, client interviews or internal recordings, it is worth checking corporate policy and Adobe's data processing terms before use.

What Video Teams Should Do

Generative Remove already looks useful for short commercial scenes, interviews, social media clips and product demos. But it is too early to build a mandatory production stage on a beta. The limits on duration, resolution and frame rate rule out a significant share of professional projects.

A practical approach is to take several typical ten-second clips and check three things: how long masking takes, how often regeneration is needed and how many credits go toward an acceptable result. If the tool consistently saves the trip to After Effects, it can be included in rough cleanup. Complex scenes and final quality control are better left to a human for now.

Story

Key Questions Answered

What Changes in the Workflow?

Processing runs in the background and should not block further editing or playback of the project. The result remains non-destructive: Premiere marks the processed clip with a special AI badge. Through it, you can repeat the generation, adjust the mask boundaries or return to the original footage. This is especially useful for small fixes that used to be too noticeable to ignore but too minor to justify a full round of compositing.

What are the key details on Beta Limitations?

Currently, Generative Remove works only with clips up to 10 seconds long. Resolutions from 480p to 1080p SDR are supported, at no more than 30 frames per second. The declared codecs are H.264 and HEVC. Adobe promises to add HDR and 10-bit color later. There is also an economic limitation: each generation consumes Adobe Firefly credits. Teams that want to build the feature into a regular production flow should take this into account.

What Video Teams Should Do?

Generative Remove already looks useful for short commercial scenes, interviews, social media clips and product demos. But it is too early to build a mandatory production stage on a beta. The limits on duration, resolution and frame rate rule out a significant share of professional projects. A practical approach is to take several typical ten-second clips and check three things: how long masking takes, how often regeneration is needed and how many credits go toward an acceptable result.

ZK
Zhemal Khamidun — CPO at Alpina Digital, product manager of AlpinaGPT. Building AI products since 2019. Hamidun News is a pet project that grew into a production aggregator with 6,000+ readers.
✦ Unified AI Workspace · Nomad

Test Frontier LLMs & Autonomous Agents in One Workspace

Run Claude Opus 5.5, GPT-6, Gemini 3.1, and DeepSeek side-by-side in Nomad AI (nomadnet.ai) — unified model routing, deep research, and multimodal workflows under one subscription.

Try Nomad AI →Launch Nomad Agent
What do you think?
Loading comments…