Start with an image or PDF
Choose a file tool, check the result, and download it without creating an account for basic tasks.
Updated
An upload form rejects your file at 11:58 PM, the deadline is midnight, and the message says only "file too large." That is the moment AttachReady is built for. You find the rule that is failing, run the matching tool, read the reported result, and download a file you can submit.
You do not need an account for basic image and PDF work. What you do need is a clear idea of which requirement you are trying to satisfy, because "make my file smaller" and "make my photo 600 × 800" are different jobs with different tools behind them.
Match the requirement to a tool
Read the receiving site's requirements first, then find the row that describes the rule you are failing.
| What the portal demands | What to do | Tool |
|---|---|---|
| A photo under a byte ceiling | Compress to a target size, then confirm the actual bytes | Compress images |
| Exact width and height | Set dimensions and a fit mode | Resize images |
| A specific format | Convert to JPEG, PNG, WebP or AVIF | Convert images |
| Tight framing or a headshot crop | Crop to pixel coordinates after orientation is applied | Crop images |
| One PDF containing photos | Lay images out as pages, in order | Images to PDF |
| A PDF too large to upload | Recompress embedded page images and verify the result | Compress PDF |
| Several documents as one file | Merge in the order you specify | Merge PDFs |
| Only some pages are needed | Extract, reorder or repeat selected pages | Split PDF |
| Scanned pages are sideways | Rotate selected pages by 90, 180 or 270 degrees | Rotate PDF |
| You do not know what is wrong | Inspect real dimensions, DPI, page count and metadata | Inspect PDF or Inspect images |
| Several rules must hold at once | Save the rules as a reusable checklist | File preflight |
The complete list with descriptions is on all tools. If you would rather hand a whole set of documents to someone as a single download, Submission package builds a ZIP with a manifest, but that tool requires an account.
Your first file, start to finish
Take the common case: a portal wants a JPEG under 200,000 bytes, and you have a 4 MB photo from your phone.
- Open the page for the requirement that is failing — here, Compress images.
- Select your file. Multi-file tools show a list, and that list order becomes the page order in the output, so fix it before running.
- Enter the byte target the portal states and change nothing else yet.
- Start the job and read the report, not just the download button. The report gives the actual output bytes and whether the target was met.
- Download the result, open it, and zoom in on small text. A file that fits the byte limit but is unreadable is not a successful conversion.
- Keep your original. Nothing here is a backup service.
Two habits prevent most failed submissions. Copy the portal's numbers verbatim: "under 2 MB" and "under 2,000,000 bytes" are not the same test. And never rename a file to change its type — turning photo.png into photo.jpg leaves the bytes untouched, and the portal will reject it anyway.
Browser-local work versus server processing
The tools take one of two paths, and the difference matters for both speed and privacy.
What stays in your browser
Preflight checks and the local inspection and image-compression controls read the file where it already sits. Nothing is uploaded for those operations, so they finish immediately and the file never leaves your machine.
What runs on the server
Format conversion, image-to-PDF, PDF compression, merging, splitting, rotation and packaging send the selected file to our processing service. These produce results a browser alone cannot, and they need the upload. Read File privacy and retention before sending anything sensitive.
Some tools use both paths. A preflight check can validate a rule locally while a conversion runs on the server, which is why the report sometimes appears instantly and the download takes a moment longer.
When you need an account
Basic processing works without login, inside the guest limits. An account adds stored uploads, job history, reusable submission rules and the package tool. Larger batches and custom package naming require an eligible higher tier. Paid checkout is not open yet, and a pricing placeholder does not grant an entitlement.
Guest server results are not kept as history, so download them before you close the page.
Automating the same work
If you process files from a script or a pipeline rather than a browser, use the REST API. If you drive AttachReady from an AI client, use MCP. Both reach the same server tools under the same access rules, so a job that behaves one way in the browser behaves the same way over the API.
When something breaks, troubleshoot by the error you actually see instead of working through the whole checklist.