After Effects

As seen in this image, the rect boundary of the right and bottom edges are not correctly displayed - there are gaps between the visual presence of pixels and the rect boundary. This is a critical issue that affects solutions that require pixel-perfect layouts. This issue affects a few 3D Mesh Types. It will be good to know, early, if this will be resolved or if this is an as-designed feature so that I and others who find this issue to be debilitating can look at alternative solutions.TIA. 

Hello. So I've been using after effects for about 4 months and had no issues while using it. But now, after about 2 minutes of opening it, it says if i want to save or don't save my file. I find this confusing because I didn't even close the window it shuts down by itself. I've even tried re-installing the plugins, clearing my memory and disk cache and now I'm looking at updating or re-installing after effects. I'm using After Effects 2025.0. My specs are 16GB of RAM, an AMD Radeon graphics card. If you can respond back with a solution that will be great.

Summary:After Effects crashes (process terminates immediately, no dialog) when interacting with the CC Particle World effect's spatial parameters — specifically when manually editing a Point control (e.g. Producer Point) or when adding/editing an expression on any parameter of this effect. Other similar particle effects (CC Particle Systems II, Trapcode Particular, Trapcode Stardust) do not reproduce this issue under identical actions.Steps to reproduce:Create a new composition, add a solid layer. Apply Effect → Simulation → CC Particle World. In Effect Controls, expand the effect's Producer Point (or any Point-type parameter). Either: (a) manually adjust/enter values for the point, or (b) right-click the parameter → Add Expression, and type any expression (e.g. value). After Effects crashes immediately.Expected result: Parameter updates normally, or expression is applied without issue.Actual result: Application terminates immediately (no error dialog shown to the user).Windows Event V

When selecting a large number of keyframes in the Timeline using marquee selection, the After Effects UI becomes progressively slower as the number of selected keyframes increases.This is especially noticeable when repeatedly adding more keyframes to the current selection.Steps to reproduce Create a composition with a large number of keyframes across one or more properties/layers. In the Timeline, use marquee selection to select some of the keyframes. Keep adding more keyframes to the selection using additional marquee selections. Observe the Timeline UI responsiveness as the number of selected keyframes increases. Actual resultThe Timeline gradually becomes less responsive as more keyframes are selected.In my case, the slowdown starts becoming clearly noticeable at around 100 selected keyframes. As the selection grows further, marquee selection and other Timeline interactions become increasingly sluggish.The important point is that this does not appear to be caused simply by hav

AE is unusable. All solutions online are not working. What is going on?I have hardly been pushing the program to it’s limits and it pretty useless right now.Cache size is 100GB. It has been cleared. Bin emptied. Comp restarted. AE updated. Purged all memory and dish cache.

This issue with no cursor showing up in Text Fields is just too much to bear any longer. I'm wondering if it's my set up or no one has noticed (highly unlikely) - very intriguing. Can we get a quick fix on this (if others notice this issue) because it's really infuriating, having to work this way. 

Your documentation suggests that users can configure their Cinema 4D installation path.https://helpx.adobe.com/after-effects/desktop/work-with-compositions/cinema-4d-compositions/cinema-4d-composition-renderer.htmlThey can’t. There is no Choose Installation button anymore. Users should be able to to configure their Cinema 4D app location in any of these ways:Environment Variable Javascript api preferences fileTo bring up the above dialog:Create a comp Go to Composition Settings 3D renderer > Cinema 4D Click on OptionsRelated Bug that needs attention: 

Hi team,I am experiencing severe performance failures and system instability across After Effects on macOS Tahoe (version 26.6). The apps are crashing, effects fail to load, previews freeze during playback, and exported/rendered video files are coming out corrupted or broken.Equipment Specs: Model: MacBook Pro (M1 Max) Memory: 64 GB RAM OS: macOS Tahoe 26.6 Software: After Effects all versions failing Main Issue: System diagnostics via powermetrics show that during playback and rendering, the Mercury Playback Engine / Metal renderer fails to engage the GPU. The hardware remains completely stuck in an idle state: GPU Active Frequency: Locked at 389 MHz (idle baseline). GPU Power Draw: ~258 mW – 335 mW (minimal power draw). High-Performance States (648 MHz – 1296 MHz): 0% activity. Because the system is not utilizing GPU acceleration, processing falls entirely on the CPU, causing heavy lag, frozen previews, effect render failures, project crashes, and corrupted media exports.Is

Scrolling font list is very slow with mouse wheel. One mouse roll equals the movement of few pixels compared to other scrollable items like Project items list for example. Please fix this.

aerender command line does not render compositions with cineware. How to fix this? New project, 1 composition, very simple project opened in cineware. When trying to render via command line, it just hangs on the line "progress...".

This is an old problem I have, and after a long time using this software, I do not see a way to solve this.1. You create a Text Box.2. You write your text.3. Press ESC as a fast way to get out of editing mode.Boom! you've lost your text.Is there any way to fix this or an alternative mode? 

EnvironmentProduct: Adobe After Effects 2025 Version: 25.6.6.4 OS: Windows 11 24H2 (Build 26100) CPU: AMD Ryzen 7 7700 GPU: NVIDIA GeForce RTX 5070 Project type: Text-heavy template with many Source Text expressions referencing other text layers across compositions.SummaryAfter Effects consistently crashes while evaluating Source Text expressions. The crash only occurs when Source Text expressions are enabled. Disabling the expressions makes the project stable.The crashes occur in two different modules:libdynamic-napi.dll TXT.dllBoth crash dumps indicate that the failure happens during TextDocument evaluation initiated by expression evaluation.Steps to ReproduceOpen the project. Enable Source Text expressions. Preview the composition or modify/enable/disable a Source Text expression. After Effects crashes.The crash is especially reproducible when repeatedly enabling/disabling Source Text expressions.Expected ResultThe Source Text expressions should be evaluated normally without crashin

IssueAfter Effects 26.3 repeatedly crashes during normal editing.The crashes are not limited to one project or one specific plugin.I have experienced crashes while using:• BMF Map Ramp• Linear Color Key• Gradient Overlay• Cinema 4D RendererThe crashes also occur during unrelated editing operations.Because the issue occurs across multiple unrelated plugins and features, it does not appear to be caused by one specific third-party plugin.--------------------------------------------------Internal ErrorSometimes After Effects displays the following message before closing:<RenderTaskManager> <1> Destructor:GetOriginalProject() is nullImmediately afterwards After Effects reports:After Effects has crashed (0,42)--------------------------------------------------Other Crash BehaviourIn many cases After Effects closes instantly without showing any Adobe crash dialog.Windows Event Viewer reports:Application:AfterFX.exeException Code:0xC0000005Sometimes Windows crash dumps are generated

I've been working in each of the ACES OCIO configurations for about a year now, but there are a number of go to effects I usually need to use which unfortunately completely clip the highlights making them unuseable. Most of the effects I've seen with this issue so far are distortion effects but also some noise/grain effects too.On a current project I really need to warp areas of the plate but mesh warp, liquify and others cause this highlight clipping issue so there are no other effects I can go to for what I need. How can I resolve this or can Adobe please fix?This is before one of the effects is appliedand this is afterThis project is ACES 1.3 Studio v1.0 32 bit, but the issue happens in the other configurations too.

Issue - filling up ram, with a preview render, never releases that ram, causes the application to generally not work.  Steps to reproduce - I use a plugin, element 3d, and preview render a long comp, that fills the ram cache, then change the comp and try to work with it. AE refuses to render anything.  Expected result - AE clears up ram, prioritizes what it is supposed to be doing. Actual result -  preview is BLACK. AE does not render anything. eventually it will crash, as the app uses more and more ram. Screen recording – this is impossible, as AE sucks down all system resources Adobe After Effects version - Version 26.0.0 (build 67) Operating system - Mac os X Tahoe 26.2 GPU driver version (Windows only) - NA Video format -  Comparative information helps us understand more about when the issue occurs:  It seems to affect projects that use large amounts of ram, and possibly plugins.  yes  AE 2025, I discovered it in December of 2025. Optional but useful: other observations: Element

Hello there,We are experiencing rendering issues with our EXRs in After Effects 25.4.Our images appear with several horizontal black lines at regular intervals, dividing the vertical image into 14 equal horizontal segments.These lines are 1 pixel high and transparent.The rendered EXRs do not present any rendering issues in Photoshop or After Effects 25.3.2.The EXRs are high resolution (4984x3584 pixels), come from 3dsmax/Vray, and are encoded in DWAB.Given that patch note 25.4 specifies improvements to EXR processing, it is possible that this is where the problem lies.No effect are in the scene, no nothing. Only the EXR sequence.The lines are not necessarily visible at the top of the composition and do not appear on all frames. However, they always appear in the same place in the composition over time.I have, of course, tried all the usual methods to remove these lines from the rendering, but I have not been successful. Purging all the data, switching to Mercury, changing the interpret

As first discovered in After Effects 26.3, third-party plugins based on the AE SDK can no longer expect to receive a valid AEGP_LayerH via AEGP_PFInterfaceSuite1->AEGP_GetEffectLayer() if the call is made while the plug-in is handling the PF_Cmd_PARAMS_SETUP command.It is unclear how this affects all third-party plugins running in AE. The side effects for FxFactory plug-ins thankfully appear to be marginal. Our plugins are invoking that function during PF_Cmd_PARAMS_SETUP in order to compute the in/out points of the effect clip by using the AEGP_LayerH in subsequent calls to AEGP_LayerSuite7->AEGP_GetLayerInPoint() and AEGP_LayerSuite7->AEGP_GetLayerDuration(). 

The viewport needs to be set to FULL res in order to track a mask.Set viewport to Half res Import a video Draw a mask to track. Track forwardThe video will play but the mask will not track.  It needs to be set at full resolution to track.After Effects v26.30Windows 11 

After Effects 2025 not working correctly – crashing/hangingWhat's wrong with my PC specs which all versions of the 2025 release of After Effects will not run successfully on my machine?Does anyone else have issues with After Effects crashing/hanging, where nothing works and then freezes?My PC spec is as follows:1 x AMD Ryzen 9 9950X AM5 Processor1 x ASUS ROG Crosshair X870E Hero AMD Motherboard1 x Phanteks XT Pro Mid Tower Case - Black1 x Noctua NH-U14S Ultra-Quiet CPU Cooler3 x DeepCool FL12 120mm PWM Fan in Black1 x Corsair Vengeance 192GB (4x 48GB) 5200MT/s DDR51 x Microsoft Windows 11 Pro1 x 1200W Be Quiet! Straight Power 12 Modular PSU1 x Palit GeForce RTX 5090 GameRock 32GB GPU1 x 8TB Western Digital Ultrastar DC HC320 3.5" HDD1 x 8TB Samsung 870 QVO 2.5" SATA III SSD3 x 2TB Samsung 9100 PRO M.2-2280 PCIe 5.0 x4 NVMe

IssueWhen applying the Detail-Preserving Upscale effect to a layer containing fine regular textures, visible seam-like boundaries appear once the Upscale value reaches 116% or higher.The image appears as though it has been divided into sections.Example texture used for reproduction:Grid effect- Grid Size: Width Slider- Width: 2- Border: 2Steps to Reproduce1. Create a new composition.2. Create a new solid layer.3. Apply the Grid effect.4. Set Grid Size to "Width Slider", Width to 2, and Border to 2.5. Apply the Detail-Preserving Upscale effect.6. Increase the Upscale value to 116% or higher.Expected ResultThe image should scale uniformly without introducing any visible boundaries.Actual ResultNo artifacts appear up to an Upscale value of 115%.The artifacts appear consistently once the Upscale value reaches 116% or higher.Visible seam-like boundaries appear, making the image look as though it has been divided into sections.Changing any of the effect parameters does not resolve the issue.

IssueAfter Effects intermittently crashes shortly after opening a project or when the first effect/render work begins on a Windows workstation with two NVIDIA GPUs from different generations (RTX 5090 + RTX 3090). Every analyzed crash is a stack overflow inside NVIDIA's Direct3D user-mode driver. Disabling the RTX 3090 in Windows Device Manager makes the same projects stable across repeated launches, without changing the project or After Effects settings.Steps to reproduceOn Windows 11, enable both an NVIDIA GeForce RTX 5090 and RTX 3090 in Device Manager. Install NVIDIA Studio Driver 610.62. The issue also reproduced with 610.74. Driver 610.62 was installed after DDU cleanup in Safe Mode. Start After Effects 26.2.0 (Build 49). Open a project that causes initial render/device work. The captured case used one image layer and one GPU-accelerated third-party effect. Wait for the project to finish opening and for After Effects to initialize/render the composition. If it does not crash, clo

suddenly my AE project didn’t work anymore. The preview playback stuck randomly within a few frames no matter what settings i chose. eventually i figured out the bug. I’m using exr renderings for my animation. I’ve got 50 frames but in between frames 30-40 are missing in the OpenExrSequence. Here comes the problem: When using the EXtractoR effect on the files but some frames don’t exist it effects the preview playback immediately. No matter the whole composition is not able to play anymore. please fix it. 

Issue - When applying the effect, “VR Chromatic Aberrations”. I get a red screen with glyph’s across the screen. Steps to reproduce - Apply “VR Chromatic Aberrations” to a layer in AE 2026. Expected result - The Effect should properly apply. Actual result -  A red screen appears with white glyph’s across the screen Screen recording – If you think it might be helpful, include a recording of your screen, showing the issue.    Adobe After Effects version - 26.3.0 Operating system - macOS Tahoe 26.5.2 Comparative information helps us understand more about when the issue occurs:  Affects all projects. Optional but useful: Upload project files, screenshots, or screen recordings that demonstrate the issue.

I saw in the new version of after effects 26.3 there is rotobrush tool and I don't have it between my tool 

We use OCIO color management in AE 26.3, but we have run into a limitation where the existing API setters for the Project Working Color Space still seem to rely on the legacy ICC workflow.Currently, we can successfully query the active OCIO space, but we are unable to set it programmatically: JSX: app.project.workingSpace currently only accepts legacy ICC profile description strings. When the project's Color Engine is set to "OCIO Color Managed", trying to pass an OCIO color space to this property fails. C++ SDK: AEGP_UtilitySuite6 provides AEGP_GetOCIOWorkingColorSpace to read the active space as a string, but the available setter AEGP_SetWorkingColorSpace strictly expects an AEGP_ConstColorProfileP (ICC profile pointer). There doesn't seem to be a symmetrical way to pass an OCIO string back into the system. Our Request: Could you please consider updating both the JSX and C++ APIs to support OCIO setters?Thank you for your time and help!