·7 min read

Filename rules that trip automated validators

The file can be perfect and still fail because the name is wrong. This is about spelling, not SEO.

Rename advice online focuses on marketing (“SEO-friendly filenames”). Portal validators focus on equality: does the uploaded string match the instruction character for character? That is a different problem — and it explains failures where size and format already look correct.

Three validator patterns we see repeatedly

  1. Exact match. The PDF says signature.jpg — not Signature.jpg, not signature (1).jpg.
  2. Prefix + serial. document-001.pdf through document-010.pdf for multi-attachment forms.
  3. Extension police. Lowercase .pdf required even though Windows hid extensions and you thought you fixed it.

Filename vs format: two different checks

Changing scan.heic to scan.jpg in Finder does not convert bytes. Automated checks open the file header, see HEIC, reject “invalid JPG.” Enable convert and rename together on Rename JPG or HEIC to JPG.

Characters that break older systems

  • Spaces → use hyphens (client-proposal.pdf).
  • Unicode apostrophes in copied names → retype in plain ASCII.
  • Parentheses from browser downloads → rename before upload, not after rejection.

Batch patterns that save time

Railway and SSC-style forms sometimes ask for ten identically structured names. Upload the batch once with a serial rename pattern on Rename file instead of editing each download manually.

Workflow

  1. Copy the filename from the official PDF — do not retype from memory.
  2. Convert first if format must change.
  3. Set rename pattern to match exactly.
  4. Download, verify name in your file manager, then upload to the portal.