Bug Reports

As of AE version 26.0.0 renders that should be rendered to an interlaced format end up as incorrect.The duration of the export is correct, though the content is playing at 200% and the rest is filled with a solid black (No transparancy)This workflow has worked for me for 20+ years. Unless I’ve fundamentally messed something up in my workflow this seems like a pretty severe bug, as the reality is that most of linair television still runs on interlaced.Create new composition at 25 fps (in PAL-cases) Add content Add composition to render queue in Render Settings change Field Render to Upper Field First Change output to Quicktime (422, 4444, animation; all have the same outcome) Render

Issue: Keyboard shortcut for “Don’t Save” in the Save Changes dialog no longer works.Steps to reproduce:Make a new empty project, make a new comp, close the project to the trigger the Save Changes dialog. Press command-D to trigger “Don’t Save”.Expected result: Don’t Save should be triggered and the dialog goes away.Actual result:Nothing happens in the save dialog. In the menubar, the Edit menu highlights because it probably thinks I’m triggering the keyboard shortcut for Edit > Duplicate.Adobe After Effects version: 26.2.0, 26.2.1, 26.3.0b53Operating system: MacOS 15.7.5 The shortcut works in AE 25.6.5. Escape (Cancel) and return/numpad-enter (Save) both work correctly.While the dialog is open, opening menus shows that many menu commands are correctly disabled, but many are still actionable and their keyboard shortcuts are still trigger-able—even if none of them do anything other than quickly highlight the menu.

When enabling Mercury Transit in After Effects, the sent Video Preview does not contain any Alpha Channel information even if the entire composition is empty. The transmitted video sends the composition overlayed over the previewed composition's background color.This is occuring on Windows, AE 25.3.0. I am checking Mercury Transit using the NDI for After Effects plugin, and monitoring both the NDI Studio Monitor and an NDI Source.Not sure if this is more a bug or a feature-request (having this be toggle-able would be great).  

Here is a breakdown of the color issues based on version and color management settings: version 24.x / Adobe color managedAfter Effects (24.6.8) direct render to JPEG → OK (No issues)After Effects (24.6.8) direct render to mp4 → OK (No issues)Media Encoder (24.6.5) direct render to JPEG → OK (No issues)Media Encoder (24.6.5) direct render to mp4 → ISSUE: The gamma is slightly different. (Is it forcibly converting sRGB to Rec. 709?) version 24.x / OCIO color managedAfter Effects (24.6.8) direct render to JPEG → OK (No issues)After Effects (24.6.8) direct render to mp4 → OK (No issues)Media Encoder (24.6.5) direct render to JPEG → ISSUE: Colors are incorrect.Media Encoder (24.6.5) direct render to mp4 → ISSUE: Colors are incorrect. version 25.x / Adobe color managedAfter Effects (25.5) direct render to JPEG → OK (No issues)After Effects (25.5) direct render to mp4 → OK (No issues)Media Encoder (25.5) direct render to JPEG → ISSUE: Colors are incorrect.Media Encoder (25.5)

This is a problem I never used to get, but on 2025 and26 if I leave AE open for more than 20 mins without cleaning my cache, apparently even the most basic of comps will decide it needs all 128gb of ram on my machine and I get this dialogue box that takes literally 150+ presses to dismiss. This is insane. At least make it so that the pop up gives me the option to clear cache or can be dismissed without machine my enter key for 2 mins.   AMD 5950, 4090, 128gb ram, windows 10, AE 25/26 all versions 

The new tools are promising, but not very intuitive. With the old root brush double clicking allowed the painting to b started immediately, but with the new tools that is not always the case. This causes a lot of confusing clicking and double clicking, opening and closing panels. Please make a clear UI for the object selection / root environment. When a footage layer is selected, choosing one of the tools should open a panel where the rotoscoping can be done.

Issue:After Effects crashes and displays the error message:"After Effects can’t continue: Encountered a GPU or graphics driver issue."This does not happen immediately on launch, but rather after opening a project and working on it for a few moments.Steps to reproduce:1. Open an existing After Effects project.2. Begin interacting with layers — for example: moving a layer, applying an effect, or previewing.3. The preview screen suddenly turns black.4. After a second or two, the error message appears and AE shuts down.Steps already taken (none resolved the issue):1. Clean installation of the latest NVIDIA driver for GTX 1650 SUPER (using “Clean Installation” option).2. GPU tested under full load with FurMark — stable temperatures, no crashes.3. GPU acceleration disabled (Mercury Software Only) — issue persists.4. Ran Windows Memory Diagnostic — no errors.5. Deleted disk cache and user preferences.6. Clean reinstallation of After Effects via Creative Cloud.7. Ran sfc /scannow — no issues f

If you're experiencing a problem with After Effects, we want to hear from you! We'd also like to know if you've found errors or omissions in our documentation. The most critical information in a problem report is how to reproduce the issue. It is challenging for us to address a problem we cannot replicate. Please provide detailed steps for us to follow to observe the problem you're encountering. Use the template below to provide us with information: Issue - A short description of the problem.  Steps to reproduce - A numbered list of the exact steps needed to reproduce the problem.  Expected result - What should happen after completing the last step. Actual result -  What actually occurred after the previous step Screen recording – If you think it might be helpful, include a recording of your screen, showing the issue.    Adobe After Effects version - FAQ: How to find the exact version of After Effects you're using? Operating system - Specify Windows or macOS, along with the version GPU

Added a master property control to the a threshold effect Level Value.Did not work at all with the project in 16 bit. Values were all over the place.Kind of works with the project in 32 bit, but the slider doesn’t work properly, neither does entering values manually.See attached video to see the janky behavior.

Gradient rendering issue (Grayscale) in Lottie/Bodymovin after After Effects 2026 (v26.0) update Issue: After updating to After Effects 2026 (v26.0), all gradients are being rendered in black and white (grayscale) when exported via the Lottie (Bodymovin) extension. The same project worked perfectly in the previous version (v25.x). Details: Setup: I am using standard Shape Layer Gradient Fills (not Layer Styles). Symptoms: All gradients in the project lose their color data and appear as grayscale in the exported JSON file and Lottie players. Suspected Cause: It seems like a compatibility issue between the new Color Management system (OCIO/Color Engine) in AE 2026 and the Lottie export data structure. Tested Workarounds: Changing Project Settings (Color Working Space to 'None') or saving the project before export does not resolve the issue in v26.0. However, the file exports correctly when opened in AE 2025. Environment: After Effects Version: 2026 (v26.0 or later) Extension: Bod

Hi Guys.I have a serious problem with the latest version of after effects (AE24) but it seems to apply to AE 23 and all version in between as well, the extractor plugin is crashing after effects for fun when applied to EXRs, no matter what i change in the settings after effects just crashes when scrubbing, caching or rendering, this is a serious problem adobe, please sort your software out, this is unusable in its current state.the only half working solution i have tried so far is turning off multiprocessing so everything takes hours to render now. WTF is going on, CPU is more than powerful enough for this, (Blade 18 ,i9 13950, RTX 4080 96Gb of ram) sort it out adobe this is appaling for"professional software" has anyone come across this, anyone know real workaround that isnt using an entirely different piece of software. 

Having issues with Layer Comments not working as should after upgrading to AE 25.2.2 (Latest) on MacOS 14.7.4. Basically layers new, duplicated, or copied, are randomly not allowing you to click into the comment field. I've not been able to find any logic to it with even sometimes completely fresh layers not allowing comments. I'm seeing it most frequently though when duplicating layers, they'll retain the existing comment but not allow you to modify it. It's not greyed the field simply cannot be clicked into. Restart of AE doesn't fix it and nor does a full machine restart. Also, some layers that might be working fine will randomly stop working and you never get functionality back. This is some pretty basic stuff Adobe, like how do you break the comment field? Causing major workflow issues with handing off and documenting projects to other animators. FIX THIS!

The new Object selection seems to mistakenly take the bounding box of the initial selection as a boundary, while the ‘object’ has moved outside. This results in unexpected cut off rotoscoped objects. Original with the human to be selectedCut off object 

Greetings! I have which I had for some time and AE worked just fine. Then suddenly it began to misbehave - freezing after several minutes of work, just a rotating circle instead of cursor. The comp is not affected, just AE is freezing. So I have to force quit it. Although I am in Moscow, Russia, not everyone here is an evil pirate) so our company pays for a license, so I reinstalled AE via Creative Cloud, removing preferences and settings, to no avail. I cannot figure out what could be a problem, it began yesterday, and not going away( No changes in configuration or setup, no obvious trigger…. No error messages, no warnings...Also, if I need to quit AE before it freeezes, it starts to freeze then, and fun lollipop begins to rotate...

Ahen rendering to QuickTime ProRes444, the processing is very slow. This is on a M3 Ultra with 96gb of RAM

I tried to change the default output path that gets assigned when I add a composition to the Render Queue, so I edited the File Name and Location Template preset.I had previously set a template named Preview as the default, so I edited it and saved it under the same name:[projectFolder]\preview\[dateYear][dateMonth][dateDay]_[projectName]_[compName].[fileextension]I also made sure the preset was marked as the default.However, when I added a composition to the Render Queue, the automatically assigned output path still used the old value.I ended up digging through the preference files and found that the issue was in "Adobe After Effects 26.2 Prefs-indep-output.txt". When I changed the old template directly in "Output Module Spec Strings Section v28", the problem was finally fixed.That section seems badly broken. It contains a lot of empty entries, and the same template appears multiple times in different slots. In this case, the template I saved as Preview was defined six times.Here is t

# Adobe Community Forum Bug Report (Form Format)## Title:“Create Multiple Compositions” produces comps that render completely black — silent failure, no error-----## Issue:Compositions created by dragging multiple MOV files onto the New Composition icon in the Project panel (“Create Multiple Compositions”) render as completely black output. Preview plays back normally. The render completes with a success status and no error message, making this a silent failure.## Steps to reproduce:1. Import multiple MOV files into the Project panel1. Select the MOV files and drag them onto the “New Composition” icon (film strip icon at the bottom of the Project panel)1. AE creates one composition per MOV via “Create Multiple Compositions”1. RAM Preview any of the created comps — video plays normally1. Add the comp to the Render Queue1. Render using any format (ProRes 4444, PNG sequence, etc.)1. Check the output — completely black## Expected result:Rendered output matches the preview with visible vide

I cannot go more than about 10 minutes without half of my dynamic link clips unlinking. The strange things is all of my dynamic links go to the same AE file. This is absolutely madding and just another thing slowing down my workflow.  Premiere 26.0.2, MacBook pro m3 max sequoia 15.7.5

Uppercase * is not uppercase when used in linked text fields or essiential graphics. Bonus wish - let me disable caps lock, im sick of the diable refresh.Other then that i Love AE ;)

There’s this very specific bug that has been happening to me since the later versions of After Effects 2025 and it’s still present on the latest 2026 release.I do a lot of transcriptions on Premiere, then convert those to captions, then convert those captions to graphics, and finally copy the graphics layers from Premiere to After Effects. This is a workflow that I’ve been doing for a while without any issues.These graphic layers are interpreted in After Effects as compositions with text layers inside. And this behavior is still true.But since later versions of After Effects 2025 (up to the current release of 2026), whenever there’s a line break (only on the first line of text) in this layer that comes from Premiere, the rest of the text just disappears. It’s still selectable and reappears if I remove the line break or convert the text layer from the original paragraph text to point text, but I just preferred if this wouldn’t happen in the first place.I’m on a 2021 M1 Macbook Pro. I’m

After updating to 22.2.1 build 3 I've got strange problem with "All Caps" feature in Character control.Some letters are "caps" and some are not, some letters can be made bold after that and some not. No issues like that were present in previous version.See attached file. If font is anything else that "Regular" "All caps" is tottaly crazy.

Hi Adobe Community,I’m experiencing an issue with Adobe Media Encoder where Hardware Encoding is not available, even though I have an NVIDIA RTX 3080 Ti installed.When I try to switch to Hardware Encoding in the H.264 export settings, I receive this error message:“Your system's hardware does not support hardware acceleration for the current settings.”

Here’s the error message after attempting to access the KSV. This error occurs when accessing the KSV via shortcut or Menu. Unfortunately, I don’t have crash reports to share.  

Subject: Text on Path — First Margin expression has no visual effect in AE English (all versions)Description:In After Effects English, the "First Margin" property of Text on Path options does not produce any visual result when driven by an expression, despite the expression evaluating correctly.The expression value updates in real time in the timeline, the expression is enabled, the text is correctly assigned to a path mask, and all other expressions on the layer are working. But the text does not scroll along the path.This issue appeared suddenly during the day — the exact same script was working correctly in AE English this morning on the same machines, and stopped working this afternoon without any change to the script, the project, or the system.The issue affects all tested versions of After Effects: CC 2024, CC 2025, and CC 2026, on multiple Macs. The exact same script works correctly in After Effects French on the same machines.Steps to reproduce:Create a new project and a new HD

Hi team — Starting a project per usual. Fine for the first hour or so. At a certain point the composition window freezes. Playing and scrubbing does nothing. I then quit, which freezes the app, making me Force Quit. This has been an issue in all versions of 26. Currently still causing issues on 26.2. I have 25.6.5 which continues to work well. Have cleared caches, checked disk settings, reset preferences. Any others experiencing this issue? This version isn’t usable. **Apple M2 Max96 GBMac OS Tahoe Version 26.3.1 (a) (25D771280a)