Skip to main content

Check a file before submission

Check a file against real submission requirements

Inspect file facts and compare them with size, MIME, page, dimension, and page-size consistency rules.

Start with a local image check when privacy matters, or run guest PDF inspection when page-level facts are required.

Run a file preflight
Choose a file
Local checks stay in your browser. Basic image and PDF processing works without login and uploads files only when you run it.

Server conversions use this mode to decide whether output is accepted.

Default: 200,000 bytes (about 200KB)

PDF page count is checked after server inspection.

Result
Choose a file to see its actual facts

Your preflight report will appear here.

How it works
  1. Choose a file and define a saved or inline submission rule.
  2. Inspect the facts that the current browser or Worker provider can verify.
  3. Read each pass, fail, warning, or unknown check with its actual value.
Current limits
  • The checker reports bytes in integer bytes and does not guess from filenames.
  • PDF inspection is bounded to 100 pages and includes page dimensions.
  • Unknown checks remain visible instead of being silently marked as pass.
Questions

Can I reuse the same requirements for a team?

Yes. Signed-in users can save owner-scoped rule templates and reuse them in the Web workbench, REST validation, jobs, and MCP.