Adobe's known-issues page for Media Encoder ties this message to four conditions at once: Adobe Media Encoder 23.1, Windows, H.264 or HEVC output, and a destination folder whose name uses double-byte or accented characters. If your setup does not match all four, the same wording on screen may have a different cause.
That scoping is the whole point of this page. The advice circulating for this error — "strip special characters out of your file names" — is far broader than what Adobe actually wrote down, and it sends people renaming projects and sequences when the documented trigger is somewhere else entirely.
What Adobe actually documented
Media Encoder's known issues list states the problem in three lines. The issue:
"An issue affecting H.264 and HEVC or H.265 exports on Windows with Adobe Media Encoder 23.1."
What triggers it:
"The issue impacts H.264 and HEVC or H.265 exports to folders with names that use double-byte characters, such as Chinese, Japanese, Korean, or extended ASCII characters, like accents and umlauts."
And what you see:
"File importer detected an inconsistency in the file structure of %filename.mp4%. Reading and writing this file’s metadata (XMP) has been disabled."
Three details are worth pulling out of that:
- Adobe names the destination folder — the folder you are exporting into. Not the project file, not the sequence, not the clip names in your bins.
- Extended ASCII is in the same sentence as CJK. A folder called
Café,MüllerorAño 2026is covered by the same line as a folder named in Chinese, Japanese or Korean. People on Latin-script systems read this as a "CJK issue" and skip the fix that would have worked. - The wording is about reading and writing XMP metadata being disabled. Adobe's page does not elaborate beyond that sentence, so treat anything more specific you read elsewhere as someone's inference rather than documentation.
Fix 1: export to a folder with a plain ASCII name
This is Adobe's first workaround, verbatim:
"Choose an export destination folder that uses only single-byte ASCII English characters (no accents, umlauts, etc.)."
The cheapest way to test it is a fresh folder at the root of a drive — something like D:\Exports — rather than editing the folder you normally use. If the export completes there, you have confirmed the cause in one pass and can decide what to rename afterwards.
One nearby failure that produces a different message: Media Encoder also refuses to encode into a folder that is not there at all. In Adobe's words, "When specifying a destination folder, ensure that the specified destination folder exists. If you specify a folder that does not exist, an error message informs you that the file cannot be encoded because the folder cannot be found." If your output path lives on a drive that was not mounted when the queue started, that is the error you get — not this one.
Fix 2: export a different format
Adobe's second workaround:
"Export to a different format, such as Apple ProRes."
That works because the documented issue is scoped to H.264 and HEVC output. In Media Encoder, ProRes sits under the QuickTime format, whose codec list includes Apple ProRes 422 Proxy, 422 LT, 422, 422 HQ, 4444 and 4444 XQ (Windows only). Premiere can also export ProRes directly inside the application, without handing the job to Media Encoder.
The catch is delivery: if what you needed in the first place was an MP4 for a client, an upload or a chat thread, a ProRes master is an intermediate step, not the finished file.
Try it right here
Runs in your browser. Your file is not uploaded anywhere.
That runs in your browser tab — the QuickTime file is read from disk, converted locally and handed back, so nothing is uploaded to a server and no second export queue is involved. The same page is at MOV to MP4 if you want it on its own.
Fix 3: for H.264 only, turn off hardware-accelerated encoding
Adobe's third workaround, verbatim, including its scope:
"For H.264 exports only: Disable hardware-accelerated encoding ."
The switch is the Performance menu in your export settings — the same menu Adobe points at when explaining how to turn hardware encoding on ("Set the Format option to H.264." / "Set the Performance option to Hardware Encoding.").
Be ready for the menu to be labelled differently than the docs you are reading. Adobe's own pages call the default entry Hardware Accelerated on one page and Hardware Encoding on another, and they call the fallback Software Encoding on one page and Software Only on another. Pick whichever software option your build shows.
Also worth knowing before you go hunting: Adobe documents that "If your system does not support certain export settings, the Performance menu switches automatically to Software Encoding." So if the menu already reads as the software option, this workaround is effectively in place and you should move to fix 1 or fix 2. There is more on that fallback in why Hardware Encoding is greyed out.
The encoding switch is not the decoding checkbox
This is where a lot of troubleshooting goes sideways. Premiere's general render-and-export troubleshooting page tells you to "Go to Preferences > Media and deselect Enable hardware accelerated decoding (requires restart) to export to H.264 or HEVC." That is decoding — how your media is read. The workaround for this error is encoding — how the output is written. They are two separate controls, and turning off the wrong one will not clear the message.
To make it worse, Adobe labels that checkbox two ways across its own pages: "Enable hardware accelerated decoding (requires restart)" and "H264/HEVC hardware accelerated decoding (requires restart)". If you cannot find the exact string from an article, look for either.
Read the encoder log instead of guessing
Media Encoder writes a plain-text record of every job, which is the fastest way to tell a failed export from one that finished with a warning. Adobe describes two files:
"AMEEncodingLog.txt: for successfully encoded jobs."
"AMEEncodingErrorLog.txt: for jobs that failed, or were stopped by the user."
On Windows, the path Adobe gives is:
C:\Users\[user]\Documents\Adobe\Adobe Media Encoder\[product version]\AMEEncodingLog.txtYou can also open them from inside the app: "To view the log file, choose File > Show Log or press Ctrl + L." and "To view the error log file, choose File > Show Errors."
How to tell it worked
Queue the same sequence again into the ASCII-named folder and check the status column. Adobe's queue table defines Done as "The item has been successfully encoded." and Failed as "Adobe Media Encoder encountered an error when attempting to encode the specified item." If the row reads Done and the error log has no new entry for that job, the export is clean — then move the finished file wherever you want it, including a folder with an accented name.
FAQ
Does this mean Premiere Pro cannot handle Chinese or accented file names? No, and that generalisation is the most common mistake here. The known issue we could find is scoped to Media Encoder 23.1 on Windows, to H.264 and HEVC exports, and to the destination folder's name. Adobe does not extend it to file names in general on that page.
Is this the same thing as "Error compiling movie"? They are separate messages. Adobe folds general render and export failures into its troubleshooting article for rendering and export issues — see what Error compiling movie actually points to for how that one is handled.
Will disabling hardware-accelerated encoding hurt my export? Adobe scopes that workaround to H.264 exports only, and recommends hardware encoding for best performance in general. Treat it as a test rather than a permanent setting: if it clears the error, you have identified the cause and can re-enable it once you export somewhere else.
Which ProRes variant should I pick for fix 2? Any of them sidesteps the H.264/HEVC scope of the issue. Media Encoder's QuickTime format lists 422 Proxy, 422 LT, 422, 422 HQ, 4444 and 4444 XQ (Windows only); 4444 XQ is Windows-only per Adobe's table. Match whatever your downstream step expects, then convert to MP4 afterwards.
I am not on Media Encoder 23.1 and I still see this message. Now what? Then the documented known issue does not describe your case, and the honest answer is that you need a different diagnosis: check the error log above, and check the current known-issues list in Adobe's official documentation, since these entries change status over time.
Quotes above come from Adobe's Media Encoder known-issues and export documentation, checked 16 September 2026. Known issues get resolved and re-scoped — verify the current status on the official page before acting. More export troubleshooting in our fix library, and the rest of the browser-side converters are at all Clapr tools.
