Feature Requests

Please add "Match Crop" to video output settings next to "match source"AND DISPLAY the current crop dimensions, currently you can only see them WHILE cropping and have to memorize themI just want to draw the crop and render everything inside of it, not sure how scaling or aspect ratio relates currently after drawing the crop, the output preview still shows it uncropped, there is no button to apply or reset it so then you have to use settings to manually adjust the output framing so i'm not sure why "crop" exists as is, its seems weird but I may be missing something

Now that the mobile Creative Cloud app is gone, is there any way to get Media Encoder to send a notification to your phone when all items have finished encoding? Bizarrely, the desktop app still has a settings panel for Notifications and instructs you to "download the Creative Cloud mobile app". Thanks.

I'm being pushed more and more into Davinci Resolve due to Adobe's inability to compete and stay up to date and keep us in their walled garden. We need AV1 support. Intel and Nvidia have had hardware AV1 encoding support for quite some time now. If I need to use AV1, I have to export as prores, then convert to AV1, doubling the export time. I shoot long videos, between 1-3 hours in length, and converting takes an insame amount of time. The filesize and quality AV1 provides is crucial so some of my workflows. 

I am not asking for AV1 to replace intraframe editing codecs, but basic decode/import support is long overdue and would immediately improve real-world workflows for a large portion of your user base.Please prioritize adding native AV1 support to Premiere Pro. It is a modern standard, and its absence in 2026 is increasingly difficult to justify.

I would like to submit a feature request for Adobe Media Encoder related to frame sizing and layout control.Currently, Media Encoder allows users to crop and scale source footage to fit an output frame, but it does not provide a way to scale footage smaller than the output resolution and position it within the output canvas (i.e., add padding or margins around the source).In many real-world delivery workflows, especially those involving mixed source resolutions, there is a need to: Shrink a source video inside a fixed output resolution Control its position on the canvas (centered or offset) Fill the remaining frame area with a defined background (black, color, or transparency) At present, achieving this requires routing assets through Premiere Pro or After Effects solely for layout purposes, even when no creative editing or compositing is otherwise needed. This adds unnecessary overhead for what is fundamentally a transcoding and formatting task—particularly in batch-processing env

Ae is using project folders AME by default will export into those folders. Whereas the export from Pr --> AME uses the last location that has been set. This is a feature request to have an optional checkbox to set up the destiantion path from Pr --> AME next to the Pr project(thanks ChWard) 

While sending files from After Effects to AME (File>Export>Add to AME render queue), the default outputpath for the file is in the actual projectfolder. While sending from Premiere, the defoult path is somewhere from an verry old project. I prefere the way Ae it is doingIs ther a way to change that?

Add XAVC LongGOP support (422/10BPP) for DCI 4K (as for UHD 3840) - MainConcept supports it already but no plugin option exists.  The larger Intra codec is fine for some purposed but not all.  Going out to other tools for delivery when the LongGOP is needed at DCI  isn't ideal. 

Hiya.  Been using Adobe since the very beginning.  Man things take a long time to happen on the development front.Here's what I want to do.  We have a CLOSED broadcast System...very limited firewall access to the WWW.I've just setup a workstation just as a render machine.  5 Team members can save a copy of their their AE projects to Designated watch folders, and it renders and delivers the files where they are needed.  Added to studio, loaded onto the server...it's great and FAST!Problem is, only I get the notifications when renders finish, fail, or whatever...as I'm the one logged into my account on the cloud.Ideally, I'd love for the senders of the files can get notifications via CC.  THis would require USER metadata being embedded in the file header I imagine...but it sounds feasable.Alternativeley, Happy for everyone in the team to get the notifications.  Can I add users to the notifications section in the media encoder setup.  I can turn the

I would love a text display in Media Encoder to show how many files are in the queue and how many are complete. This could be a preference you can turn on and off in Encoder. This would be immensely helpful when rendering large amounts of files - like when creating proxy files within Premiere Pro. There is currently no way that I know of to check how many files are in the queue and I would use this function to double check I have every file accounted for.

When exporting multiple files, we can batch change the file location but not the file names.When having multiple exports for different resolutions or ratios, dynamic naming using placehoders would be great. This could be possible by using placeholders directly in the sequence name (e.g. Sequence-1_%SeqName%) which gets replaces on export (maybe also through a command "replace wildcards in project") or during export with naming presets that can be applied.On naming conflicts, these exports could be grayed out with a warning symbol, still allowing manual changes. Placeholders that would be great are: Sequence nameResolutionAspect RatioFrame rateFrame count/Durationany (custom) Metadata fieldCustom prefix/suffix Especially batch exports would benefit from this.

Hi,   I am trying to use a watch folder to export out hundreds of proxies during a shoot day.   The workflow is like this:   Action filmed -> Copied off camera card to Hard drive -> *Hard drive folder will be a designated "Watch folder"* -> AME will be auto encoder this raw footage to a proxy preset that will live locally on the comp for quick edits during the shoot.This all works amazingly well, however when i copy over multiple clips into the Watch folder, AME encodes them, then places each "source" clip, into its our folder. Please see screenshot below     Is there any way to change it so that they all dont appear in their own subfolder?   Many thanks!     [Moderator note: moved to proper forum.]

Watch folders should be able to also watch and encode from subfolders. Having all footage in one folder or having to create multiple watch folders is very inefficient and impractical when dealing with a lot of footage.I would also like to be able to use Media Encoder to automatically render small HEVC backup files of all new footage to be sent to offsite backup. Setting my whole video project directory as a watch folder with subfolders would allow this; the output folder would be easy to back up.

I think I would find value in a feature that would allow me to expand the preview window in media encoder to an undocked resizable window and/or second display.  Mainly because Id like to see some ore detail while its processing so that while it works in the background, and I am doign something else, I can maybe catch something that doesnt look right. As an example, I am exporting a 50 min video right now, with some heavy effects,  media encoder is running for an estimated 7 hours to process this.  I would love to be able to see the preview window expandable incase soemthing happens I was not expecting. Currently undocking doesnt seem to allow you to make the preview of the video resizable.

It would be nice to have the Log be a window we can attach.  It would make troubleshooting easier to watch the flow.

Requesting Elapsed Encode Time column for each render, not just live encoding time or digging in the log.

Hi - I need to know if the Adobe Media Encoder supports WebM files, and if it can convert a WebM file (of at least 250mb) to a standard video file, such as mp4 or Quicktime.Thank you!

So I recently stumbled into a bit of a rabbit hole around the moov atom in .mp4 files, basically a piece of metadata at the container level that tells the browser how to play the video.I export all my videos using Adobe Media Encoder (not sure which version but i believe 2025 non beta), then upload them to BunnyCDN to use as direct .mp4 links for autoplaying videos on my Framer site. But I noticed that some videos, especially longer ones, just wouldn’t autoplay properly in Safari, while working fine in Chrome and Firefox.After digging into it (and talking to Bunny), it turns out the moov atom needs to be at the start of the file for proper streaming and playback. Safari especially doesn’t like it when it's placed at the end, which, apparently, Media Encoder sometimes does without any way of changing it.This is especially important for, as I understand it:Autoplaying background/autoplaying videos on websites (like I’m building in Framer). Even though most videos of mine work, i suspect

Dear Mediaencoder team,Can you please inlude SWF to MP4 as a conversion option on media encoder.

Please add support in Adobe Media Encoder (AME) for generating audio peak files (.pek) and transcripts in a dedicated preprocessing phase. This would allow AME to operate as a headless preparation tool, ensuring assets are ready for immediate use in Premiere Pro without needing to open the project manually.

Hi there,Just a small request - can we please have the option in Encoder to 'Import into Project' We have this functionality within Premiere, but not in Encoder and I'm not sure why.Would be handy.Thanks,Matty

I would like to be abe to add fade in/out on Video and Audio tracks.  It's something I used regularly in Sorenson Squeeze and I would find it very useful in Media Encoder.

Hello Adobe Community and Product Teams, I want to share an idea aimed at significantly improving our experience with resource-intensive Creative Cloud applications, such as Premiere Pro, After Effects, Media Encoder, and potentially others. --- ### **The Current Problem: The Local Performance Bottleneck** We love the power of Adobe tools, but many of us face major challenges: * **Prohibitive rendering and encoding times:** Hours of waiting for complex projects, which hinders creativity and productivity.* **High hardware requirements:** The need to invest in expensive workstations to achieve acceptable performance.* **Slowdowns and lack of fluidity:** Choppy previews, less responsive interfaces on heavy projects, even on good machines.* **Lack of flexibility:** Difficulty working efficiently on less powerful machines or on the go. These factors limit our ability to fully exploit the potential of the software and meet our deadlines. --- ### **The

It would be nice for Adobe Media Encoder to have naming tokens just like within the After Effects Renderer, for example when exporting a composition named [projectName]-[width]x[height]-[YYYY-MM-DD] it will automatically name your export to the project name + size of the composition + the render date.

It seems like an oversight that Medai Encoder cannot ingest DNG photos to batch convert to either JPG or PNG. Please allow compatibility to do this. I hope it's not too complicated to add.Also, I know there is a workaround using Photoshop.  File > Scripts > Image processing. But you have to select an entire folder, rather than dropping in specific photos to convert. Maybe others will agree this addition seems like a given?