Read a maximum as a maximum, not a requested exact size
An upload instruction saying 'up to 150KB' normally sets a ceiling, but read the actual wording because some fields also specify a minimum. This tool aims below a maximum; it does not fill an otherwise suitable file with extra bytes to hit a precise number. A smaller result is only useful when it also meets the other conditions.
For a small photo or scanned item, note the required width, height and accepted extensions before processing. If the site says JPEG, a small PNG is not automatically suitable. If it needs a minimum pixel width, a heavily reduced image may no longer qualify. Keep the whole set of requirements visible while you choose the next step.
This preset uses decimal kilobytes
Here, 150KB means 150,000 bytes and the target is strict: the result must be smaller than that. A binary 150KiB limit would mean 153,600 bytes. This preset deliberately uses the smaller decimal interpretation rather than relying on a rounded file-manager label.
Check the final file's properties and use the compatibility checker when the destination supplies its own exact figure. Do not infer acceptance from a displayed value such as 146KB without knowing how that display was calculated. A precise byte count is more reliable at the boundary, especially when a website rejects a result that appears to be within its limit.
Choose conversion and compression in the right order
If the original format is not accepted, establish the required output first. Converting an image can change its size, so measuring only the original before conversion does not tell you whether the final file will fit. Use an appropriate converter, open the output and then apply a size target if it is still needed.
An already-small file is not silently converted just because you used this page. For example, a valid WebP below the target remains WebP when its bytes are preserved. That is useful when the destination accepts it, but not a solution for a JPEG-only field. A format check and a size check answer different questions.
Start from a readable source instead of a degraded copy
Repeatedly compressing yesterday's compressed version is rarely a sensible first choice. Return to the original photo, scan or exported document when it is available. Compare the source at a useful viewing size so you know which details must survive the reduction.
If the image includes excessive empty canvas, consider whether a permitted crop would remove irrelevant material without changing the requested content. This tool does not crop for you. For documents, keep the necessary edges and context visible; a cropped account heading or incomplete certificate can create a more serious problem than the extra bytes it removed.
What the image engine is allowed to change
The browser engine can re-encode supported image pixels and reduce dimensions while searching for a small enough output. It does not claim that every change is visually lossless. JPG and WebP quality can change, while a PNG may need fewer pixels to become significantly smaller.
The processing loop has a limit and stops with a truthful error if the target is not reached. It does not label the closest oversized attempt as a success. When a result is offered, its measured size has passed this preset's ceiling, but you still need to judge whether the visual result is useful for the receiving task.
Keep transparent artwork from changing unexpectedly
Before converting anything to JPEG, think about transparent areas. The page offers an explicit white or black background choice where the engine needs one, rather than pretending JPEG can retain transparency. Review pale edges, logos and signatures against the chosen fill.
Flattening transparency is not background removal. If the source is a photograph of a printed signature on grey paper, that photographed grey remains image content. If a specific appearance is required, prepare the source appropriately in an image editor and then test the size of the exported copy. Do not expect a byte-target tool to understand which marks belong to the document.
Understand the narrower options for PDFs
PDFs are repacked losslessly rather than automatically downsampled into page pictures. That protects the distinction between a document and a screenshot of its pages, but it also means some scans will not shrink enough. A 150KB ceiling can be demanding for several detailed pages.
Try a more efficient original export when one is available, and inspect all pages afterwards. Do not remove required content to force a pass, and be cautious with signed or interactive PDFs whose features may be affected by editing. If the receiving organisation needs the whole document and it cannot meet the cap, ask about the correct alternative route.
Review and submit the intended version
Open the downloaded file and check its actual format, size and dimensions. Look closely at the smallest relevant text or image features. A correct byte count does not make a blurred date, broken thin line or unreadable reference number acceptable. Keep a copy that you would be comfortable asking another person to read.
Return to the receiving form and explicitly select the new version. Some file pickers continue to show an older selection after you create another download. Read the next error, if any, before processing again. Once size is no longer the issue, repeated compression can make the file worse without addressing an unsupported format, wrong dimensions or a failed account session.
Questions that come up
Can I upload the file here without it leaving my device?
The processing itself takes place in your browser, and the selected source is not sent to our server. Inputs still have local resource limits, including 25MiB per file. Your browser and device must be able to decode the supported format before the tool can produce a verified result.
What happens when the original is already below 150,000 bytes?
A validated file already strictly below the preset may be returned without altering its contents. That avoids unnecessary quality loss, but it also preserves the original format. Check whether that format is accepted by the receiving website instead of assuming a small file has been converted.
Does the tool check a minimum file size too?
This preset only targets the upper ceiling. A receiving field may impose a minimum or other rules, which must be checked separately. Do not treat a very small successful output as a complete portal-compatibility verdict. Read the whole instruction and inspect the downloaded file.