The messages, and what each one actually means
Since version 1.6 of CM/ECF, released on 21 December 2020, the filing system inspects the internal structure of every PDF before it will accept it. These are the rejections it returns, quoted from the District of New Mexico's own page:
ERROR: this document has security measures in effect
The file is encrypted or carries a permissions password. ⚠️ This happens more often by accident than on purpose — some document systems and scanners apply a permissions password by default, and a file can be locked against editing while still opening with no prompt at all.
ERROR: Document contains code which may cause an external action (such as launching an application). This PDF document cannot be accepted.
There is JavaScript or a launch action inside the file. Form templates and documents exported from certain systems carry these without anyone asking for them.
ERROR: Document is malformed or contains code which may cause an external action (such as launching an application). This PDF document cannot be accepted.
The structure itself does not comply with the PDF standard, or the same script problem applies. ⚠️ The court names specific culprits: fillable PDFs made on Mac OS X in Safari, and files produced by Word on a Mac using "Best for printing" — for which it advises choosing "Best for Electronic Distribution" instead.
The full list of what CM/ECF refuses: encryption or password protection · JavaScript · anything that can launch an external application · internal attachments · embedded audio or video · malformed structure · fillable form fields.
🔑 Your PDF reader will open a file containing every one of those. Opening is not the test, which is why the rejection feels arbitrary.
"Save As" does not flatten anything
This is the step almost everybody gets wrong, and it is worth being blunt about.
Saving a fillable form as a PDF writes a new file that still contains live form fields. The court is rejecting the fields, not the file format, so saving again changes nothing. The Bankruptcy Court for the District of Nevada puts it directly: do not use Save or Save As from the File menu when saving a document to PDF.
Flattening means the values are painted permanently into the page and the fields stop existing. Printing to a new PDF does that. Save As, Export and "Download as PDF" generally do not.
⛔ The fix that quietly breaks your filing
There is an obvious shortcut here, and it is wrong often enough to be worth a warning.
Converting every page to an image definitely removes form fields, scripts and attachments — nothing survives it. It also destroys the text layer.
A great many districts require filings to be text searchable, and several require that documents be converted directly from word processing software rather than scanned at all. Rasterising a brief satisfies the validator and breaks the local rule, so you trade a rejection you understand for one you do not — and that second one may arrive later, from a clerk, rather than immediately from the system.
⚠️ So: flatten the form fields and leave the text alone. Only rasterise when the document is already a scan, or when nothing else has removed whatever the validator is objecting to, and check your district's rule on searchable text before you file it.
What to do, in order
- If it says "security measures in effect" — the protection has to come off the file. Remove PDF protection does it in your browser.
- If it is a fillable form — flatten the form fields using the field mode. The values are painted in, the fields disappear, and the text stays selectable, which is what the local rules want.
- If it is malformed, or came from Safari or Mac Word — re-export it with "Best for Electronic Distribution", or rebuild the file, which rewrites the structure without touching the content.
- Only then consider rasterising, and only after reading your district's rule on searchable text.
⚠️ The error message will not tell you which of these applies. It names a category, not a cause. Working down this list in order is faster than guessing, because each step is cheap and the first two cover most rejections.
And while you are here: the size limit is probably not what you were told
A different CM/ECF rejection, for a different reason, catches people just as often. Every district sets its own PDF size limit and the published guidance is frequently out of date — we found 7 of 23 figures stale within a week, including a court whose own FAQ understated its limit by a factor of seven.
Nothing on this page leaves your computer. Every tool linked here runs in your browser, which on a client's filing is the point.