Troubleshoot file processing
Resolve unsupported formats, unmet byte targets, expired files, quota errors, and API authentication failures.
Updated
Start with the reported rule
Check whether the problem is file format, size, dimensions, PDF pages or naming. A successful conversion does not mean an unrelated receiving website must accept it. Compare the downloaded result with that site's latest rules. Our upload error guide gives a step-by-step checklist.
| Symptom | What to try |
|---|---|
| Unsupported or invalid file | Open the original in its source app and export a supported format. Changing the extension is insufficient. |
| Size target not met | Reduce image dimensions or quality; for scanned PDFs, try deep compression. Check readability. Use best-effort only if an over-target result is useful. |
| PDF rejected | Check encryption, attachments and active content. Export a plain PDF from the trusted source app if you have permission. |
| Quota exceeded | Wait for the daily allowance to reset or sign in for account limits. Repeated retries can consume attempts. |
| Expired file or download | Re-upload your original and run a new task; account tool storage is temporary. |
| API 401 or 403 | Check the Bearer key, tool permissions and account entitlement. Never place an API key in a public browser bundle. |
| Async job still running | Poll the returned job endpoint with bounded backoff. Reuse the original idempotency key after a connection failure instead of creating duplicate work. |
Ask for help without sending private files
Email support@attachready.com with the tool URL, approximate time, error code, browser version, format and approximate size. Include a job ID if available. Do not send API keys, passwords, identity documents or confidential attachments. A minimal non-sensitive sample is more useful than your original private material.
For integrations, the API reference and MCP guide describe discovery, authentication and the shared job lifecycle.