<ul>
<li>Are you exporting to h.264? Try rendering to a master file in a intermediate codec like ProRes, Cineform or DNxHR. Rendering to h.264 involves referencing multiple frames to create the intermediate frames. When those frames have to be rendered first it adds an extra drain on resources, particularly memory.</li>
<li>Is the computer hitting the limits of available memory? This will <em>exponentially</em> slow things down. Check on the available RAM at render time, and if it's getting full you need to take steps to reduce your memory usage. One way is to pre-render sub-comps, another is to make sure images you use are appropriately sized for the output. Time-based effects like echo are big RAM hogs, you may have to pre-render layers with these applied.</li>
<li>Learn how to use the command line renderer <strong>aerender.exe</strong> (just plain aerender if you're still on a mac). This is between 10% and 4000% (no lie) faster in my experience than Media Encoder, particularly if you have enough memory to <a href="https://blob.pureandapplied.com.au/finally-managed-to-peg-my-cpu/" rel="nofollow noreferrer">spin up multiple instances</a></li>
<li>since you're using the command line now, why not get MOAR COMPUTAHS on the job? Aerender can be used over the network, so if you have other machines that you can borrow you can create a render farm. You can also use the GUI network renderer if you're not ready to become a fully fledged command line ninja, but I will be silently judging you.</li>
<li>all of these steps assume that the workstation you have is a constant. The single best thing you can do is to get a <a href="https://www.schoolofmotion.com/tutorials/after-effects-computer" rel="nofollow noreferrer">better computer.</a> Or several.</li>
</ul>

CC BY-SA 4.0
2019-12-03T06:25:37.450Z
Awesome, thank you for the explanation. I will give the command line a try. I do get available memory warnings and need to restart to avoid that.
would really appreciate it if you can share some learning docs or videos.
Again, thank you very much.
Dhaval Jardosh
CC BY-SA 4.0
2019-12-03T11:15:12.820Z
If it's memory that is causing the problem then things like pre-rendering and project management will make the most difference.
stib
CC BY-SA 4.0
2019-12-03T06:12:55.197Z
2019-12-03T06:12:55.197Z
stib
<p>I'm using After Effects to create videos and export it via Adobe Media Encoder, but even a 2 min video takes a very long time to export.</p>

<p>I do use Motion Bro plugin, to get some effects, but that's just a transition effect to change from one screen to another.</p>

<p>How can I make it quicker?</p>

<video><after-effects><adobe><adobe-media-encoder><export>
Video Exporting takes too long in Adobe Media Encoder
Dhaval Jardosh
# Video Exporting takes too long in Adobe Media Encoder

(Asked by: username_0 on 2019-12-03)

I'm using After Effects to create videos and export it via Adobe Media Encoder, but even a 2 min video takes a very long time to export.

I do use Motion Bro plugin, to get some effects, but that's just a transition effect to change from one screen to another.

How can I make it quicker?

**Tags:** video, after-effects, adobe, adobe-media-encoder, export


---

## 1 answers

### Answer by username_1 on 2019-12-03. Score: 2 | Accepted answer

* Are you exporting to h.264? Try rendering to a master file in a intermediate codec like ProRes, Cineform or DNxHR. Rendering to h.264 involves referencing multiple frames to create the intermediate frames. When those frames have to be rendered first it adds an extra drain on resources, particularly memory.
* Is the computer hitting the limits of available memory? This will *exponentially* slow things down. Check on the available RAM at render time, and if it's getting full you need to take steps to reduce your memory usage. One way is to pre-render sub-comps, another is to make sure images you use are appropriately sized for the output. Time-based effects like echo are big RAM hogs, you may have to pre-render layers with these applied.
* Learn how to use the command line renderer **aerender.exe** (just plain aerender if you're still on a mac). This is between 10% and 4000% (no lie) faster in my experience than Media Encoder, particularly if you have enough memory to [spin up multiple instances](https://blob.pureandapplied.com.au/finally-managed-to-peg-my-cpu/)
* since you're using the command line now, why not get MOAR COMPUTAHS on the job? Aerender can be used over the network, so if you have other machines that you can borrow you can create a render farm. You can also use the GUI network renderer if you're not ready to become a fully fledged command line ninja, but I will be silently judging you.
* all of these steps assume that the workstation you have is a constant. The single best thing you can do is to get a [better computer.](https://www.schoolofmotion.com/tutorials/after-effects-computer) Or several.

> **Comments:**
> **username_0**: Awesome, thank you for the explanation. I will give the command line a try. I do get available memory warnings and need to restart to avoid that. would really appreciate it if you can share some learning docs or videos. Again, thank you very much.  
> **username_1**: If it's memory that is causing the problem then things like pre-rendering and project management will make the most difference.  

---

