When I need to prepare a photo for an upload form, I want a smaller copy that meets the requirements without making the picture harder to read. That is the job I am looking at here, not finding another service that wants an account before it will let me download my own image.
I get tired of recommendations that treat the smallest possible file as the only result worth discussing. A file can pass an upload check and still be a poor version of the picture. If lettering has become difficult to read or fine edges look damaged, meeting the limit has not solved the whole problem.
My starting point would be the form’s actual requirements. File size and pixel dimensions are separate things, and I would check both before changing anything. There is little point reducing the width to save space if the receiving site requires dimensions that the new copy no longer meets. Equally, keeping unnecessary resolution while pushing compression harder is not automatically the better choice.
Decide what the smaller copy has to preserve
For an ordinary photo, I would check faces, fine edges, and any small lettering at the size people will actually view it. The saved file needs that inspection, not just a glance at a number showing how much space disappeared. I do not need every upload to be suitable for a large print, but I do want it to remain useful where it is going.
Transparency deserves a separate check. A PNG can come out as a JPEG with this tool, which may be acceptable for a regular photograph. A transparent logo is a different matter. I would not assume that a smaller download is interchangeable with the original just because the main subject still looks right.
That is also why I would keep the original untouched and treat the compressed version as an upload copy. The size restriction belongs to the destination. It does not mean the original should be replaced.
For several pictures, I would start with a detailed one rather than immediately applying the same settings to the whole group. Batch processing is convenient, but I would rather inspect a demanding example first. It is a small check that keeps convenience from becoming the only consideration.
Use the limit setting, then inspect the result
For this fairly narrow job, this free image compressor has the relevant controls. It accepts JPG, PNG, and WEBP files, offers either a quality setting or a target file size, and lets you download the result. It also supports batch processing.
The practical attraction is that it is free, with no signup or watermark. Processing happens in the browser rather than by uploading the photos to a server. Those are useful details for an everyday file-preparation task, although they do not remove the need to check what comes out.
If a form specifies 200 KB, I would select “Fit a size limit” and enter that amount instead of repeatedly guessing at a quality setting. For a strict 1 MB allowance, I would leave some headroom rather than aim directly at the boundary. Getting as close as possible to the ceiling is not the objective.
If the result still needs to be smaller, the maximum width control is worth considering before making compression more severe. I would reduce resolution that the upload does not need, while keeping the required dimensions in mind. Then I would inspect the downloaded copy again, including its format if transparency matters.
I would keep this as a straightforward option for the familiar oversized-image problem, not a reason to stop checking files or start paying for a photo editor. The useful outcome is an acceptable upload copy with the original still available, not merely a smaller number. When you prepare images for forms, which tends to cause more trouble for you: the file-size limit, the required dimensions, or keeping the important details readable?