Prepare an image for upload: format, dimensions, and the final file

Turn the upload instructions into separate checks

An image is ready to submit when its format, pixel dimensions, file size, and visible content all meet the receiving system’s requirements. Making the file smaller solves only one of those problems. Start with the instructions on the actual upload form, then keep the original file under a separate name.

Suppose a form asks for a JPEG image, exactly 1,200 × 800 pixels, no larger than 200,000 bytes. These are hypothetical requirements used to explain the workflow, not the rules of a particular service.

Requirement	What to record	What would fail this example
Format	Accepted file types	A small WebP file when only JPEG is allowed
Dimensions	Width, height, and whether limits are exact or minimum	A 1,200 × 900 image
File size	Maximum bytes per file or for the entire attachment set	A 210,000-byte JPEG
Content	Required subject, visible details, and cropping rules	Missing text or a cropped-out part of the subject

If the instructions say only “200 KB,” look for a more precise size definition or the form’s validation message. Tooliv’s displayed sizes may be rounded. A file close to a limit should be checked using its actual byte size, rather than the number shown in a thumbnail.

Choose the right starting file

For a photo or screenshot, use the original export when available. A copy saved from a messaging preview may already have fewer pixels or visible compression artifacts. Converting that copy to another format will not recreate the missing detail.

For a PDF, decide whether the receiver needs the page’s appearance or its editable text. PDF to image renders a page into pixels; it does not extract a spreadsheet or perform OCR. Mozilla’s PDF.js examples explain how the chosen rendering scale determines those pixels. The PDF resolution guide helps choose a suitable output before further image editing.

If the existing image already meets every requirement, keep it. An extra conversion introduces another result to inspect without necessarily improving the submission.

Resolve the aspect ratio before changing the dimensions

Our hypothetical target is 3:2. A 3,600 × 2,400 source has the same ratio, so reducing it to 1,200 × 800 preserves its proportions. The pixel count changes from 8,640,000 to 960,000: one ninth as many pixels. This is a calculated relationship, not a measured reduction in encoded file size.

A 4:3 source needs a different decision. Filling a 3:2 rectangle requires cropping some content, adding a border, or distorting the image. Check what the receiving system permits. Tooliv’s resizer draws the image at the dimensions you enter; entering a different ratio is not an instruction to crop around a face or a document automatically.

Use the ratio lock when the proportions should stay unchanged. If cropping is required, prepare that crop in an editor first. Adobe explains the distinction between changing pixel dimensions and changing physical print size; for an upload specified in pixels, the pixel dimensions are the relevant measurement.

Check the format after every operation

Tooliv’s image resizer saves PNG. For the JPEG-only example, the next step is to select JPEG in the image converter, then inspect the new file.

For a transparent logo, the decision may be different. JPEG does not retain alpha transparency, while PNG does. Those format capabilities are documented in MDN’s image guide. If the receiver requires JPEG, prepare an intentional background and inspect the edges; do not assume a transparent area will look right after conversion.

The compressor can also change the output format: it attempts WebP encoding for PNG inputs and can retain the original if encoding does not produce a smaller file. The format shown beside the final result matters. The format selection guide covers this choice in more detail.

Reduce bytes only after the required pixels are settled

Open the resulting file in the image compressor if it still exceeds the limit. For our example, enter 200 in Target size per image (KB, optional): Tooliv uses 1 KB = 1,000 bytes. It tries lower quality settings up to the quality you selected, while keeping the pixels unchanged. Leaving the target empty uses the selected quality directly. Quality is an encoder setting, so 80 does not mean a 20% reduction in bytes or an 80% visual match.

The file’s status reports whether the final bytes meet the target. An original already within the budget is kept. If the target is not met, review the resize link and the permitted dimensions instead of treating a downloadable result as an accepted submission.

Follow the size and quality troubleshooting sequence if the file stays too large. Stop reducing quality when required details become unreadable. At that point, review the permitted dimensions, formats, or alternative submission routes.

Inspect the file you will actually send

Download the candidate, reopen it, and check the format, width, height, and bytes. Look at small text, thin lines, faces, and any required identifier. For multiple PDF pages, compare the page numbers and file count with the original. A ZIP of ready compression results can include files that did not meet the target; check their individual statuses and unpack the archive before uploading where separate images are required.

Finally, use the receiving form’s preview if it offers one. A successful download from a converter confirms that you obtained a file; acceptance depends on the receiving system and the content it requires. Keep the original and clearly name the approved version so a later upload does not accidentally use an earlier attempt.