Skip to main content
Participant
January 8, 2026
Open for Voting

Proposal for a Unified Creative Engine: Integrating After Effects Tools Directly into Premiere Pro

  • January 8, 2026
  • 3 replies
  • 214 views

I have used Adobe for over 12 years and its been great. I work with a team of editors and our needs have changed over time and we need a better solution then what adobe is currently offering. I would switch to some thing else if i could right now but can not. I am stuck with adobe for now so i am writing this hoping it will spark some kind of change. 


The Problem:
Currently, the "round-trip" workflow between Premiere Pro and After Effects via Dynamic Link is becoming a significant bottleneck for modern creators. While Dynamic Link was revolutionary years ago, the requirement to manage separate project files, deal with "Media Offline" link breaks, and wait for background render engines to initialize is no longer competitive. In an era where "all-in-one" ecosystems are becoming the standard, the friction of switching between two heavy applications is a major pain point.

The Solution: I am proposing a Unified Workflow. Instead of After Effects being a separate application that requires a separate save file, Adobe should integrate the After Effects compositing engine as a dedicated "Compositing Workspace" or "Page" within Premiere Pro—similar to how the Lumetri Color panel integrated SpeedGrade.

Why This is Crucial for Adobe’s Future:

  1. Project Management: Eliminating the need for separate .aep files would drastically reduce file bloat and the risk of broken links. Everything should live within one project container.

  2. User Retention: Many long-time Adobe users are currently migrating to competitors (like DaVinci Resolve) specifically because the "single-software" workflow is faster and more stable. By unifying these tools, Adobe would remove the primary reason users are leaving the ecosystem.


  3. Performance:
    A unified engine would allow for shared RAM previewing and smarter caching, ending the "waiting for link" lag that currently disrupts the creative flow.

Conclusion: Adobe has the best motion graphics and editing tools on the market, but they are currently trapped in silos. By listening to the community and unifying these programs, you aren't just adding a feature—you are modernizing the entire post-production philosophy. We want to stay with Adobe, but we need a workflow that keeps up with the speed of modern content creation.

3 replies

Participant
January 10, 2026

well, the file bloat i am referring to, is not the size of the files. its the fact i have even think about a long list of files to manage and have to keep track of them and i have to title them and then i have fix all the others that the other editors create so it just turns into one big mess and no one likes working on mess. 

 

I like to think like this - The best part, is no part.
I am just saying simplifying the process of creating.

MyerPj
Community Expert
Community Expert
January 8, 2026

I think Adobe integrated a portion of the AE code, it may be called 'little' or such, and it runs the mogrts in PP.

But I can't see how: <<Project Management: Eliminating the need for separate .aep files would drastically reduce file bloat and the risk of broken links. Everything should live within one project container.>>

 

This seems wrong to me, if there is no .AEP, and it's all in the .PrProj, that's gotta be a bigger file right? The opposite of what you are proposing.

 

I'd be happy for now if they would break out the Warp Stabilizer data into sidecars and at least get rid of that bloat.

 

Otherwise, better integration is always welcome. 🙂

R Neil Haugen
Legend
January 8, 2026

I totally understand the frustration with Pr/Ae workflows. No question there.

 

However, combining the two apps would basically require a nearly complete rebuild of the Ae 'engine', the code-running bits, and a massive set of changes in Premiere. Just being real.

 

It's been quite clear that Ae and Pr do not run much similar code. Nearly every tool and effect in Ae has no corollary in code in Premiere. Nothing at all, even the things that 'seem' similar have entirely different code and processing order actions in Ae.

 

Which like many users, I assume is part of the issue with Pr/Ae workflows.

 

I work in Resolve also, and some say "Well, BM got fusion into Resolve" ... yes, true, sort of. It's "Fusion light" as many of my Resolve and Fusion using acquaintances call it. Not really the full capabilities of Fusion stand-alone.

 

And past that, the blame thing is so different in use than any other "page" of Resolve, I have more trouble using that than I do AfterEffects. Plus color management between the other pages of Resolve and Fusion is ... problematic. For experienced Resolve users.

 

To recap, emotionally I would love your suggestion to be done. No question.

 

Realistically, I can't see it ... and wonder how useful it would actually be the first two-three years it was implemented. Sigh.

Everyone's mileage always varies ...