G2

Jasdeep Singh S.

Software Developer

Small-Business (50 or fewer emp.)

11/7/2026

"Fast, Reliable Encoding—But No CI-Friendly CLI"

4/5

What do you like best about Adobe Media Encoder?

I like Adobe Media Encoder’s watch folders and queue. Watch folders save me the most time: new screen recordings are automatically turned into compressed MP4s ready for a PR or ticket, with no manual steps, and I can batch a full release’s demo videos in the queue. GPU encoding cuts wait time from minutes to seconds, and the output quality stays good even at small file sizes. I also like that presets are easy to save and share, so our web, mobile, and docs videos use consistent size and bitrate settings. The simple UI and easy setup work well for everyday encoding, and new developers can import the presets and get started. I find Adobe Media Encoder reliable, fast, and easy to use for our dev team. Review collected by and hosted on G2.com.

What do you dislike about Adobe Media Encoder?

Adobe Media Encoder has no official CLI or API and no Linux version, so I can’t run it on build servers or in CI and still rely on FFmpeg for automated encoding. It’s heavy on CPU and RAM, which slows our machines while it runs. Failed queue items sometimes give vague error messages that are hard to debug, and a Creative Cloud subscription is costly just for encoding. A headless CLI with Linux and Docker support, presets exportable as JSON or YAML, clearer error logs with exit codes, resource limits, built-in AV1 and HLS/DASH output, and a cheaper standalone plan would help. Review collected by and hosted on G2.com.

What problems is Adobe Media Encoder solving and how is that benefiting you?

I use Adobe Media Encoder to shrink huge, inconsistent recordings and exports while keeping quality. Shared presets give developers consistent settings, so we no longer debug playback issues from odd codecs or bitrates; smaller files are easier to share and don’t slow page loads or bloat app bundles. Review collected by and hosted on G2.com.