Use these image tools to prepare a copy that suits the receiving website: a different format, a smaller file or a normalised orientation. Begin with the best source available and a clear reason for the change. A photograph, a screenshot and a transparent logo may need different treatment even when the upload error sounds the same.
Identify the picture and the requirement together
First establish the real source format, the current dimensions and the receiving rules. An image that opens on your phone may be HEIC, while a downloaded website picture may be WebP. The form’s accepted list is what determines whether a conversion is necessary. Familiarity with an extension is not a compatibility test.
Next consider what the image contains. Tiny lettering, fine line work, soft photographic detail and transparent edges react differently to re-encoding. A smaller copy is only useful if the information needed by the recipient survives. Keep the original so you can change your approach without repeatedly editing an already reduced version.
Choose a converter that matches the source
The dedicated routes include HEIC to JPG, WebP to JPG, PNG to JPG and JPG to PNG. They create a new file in the requested output format where the source can be read. They do not merely replace the filename ending, and they can refuse inputs that do not match the selected source format.
If an image has already been converted by a phone’s sharing workflow, check the file that the picker actually supplies. It may no longer be the format you expected. Selecting a JPEG on the HEIC page is a different issue from a broken HEIC decoder. The type checker can help separate those cases before you try again.
Decide whether transparency must survive
A transparent logo or product cut-out can sit on different backgrounds. Converting it to JPEG replaces that transparency with a solid colour, so choose the intended background before processing. Check shadows and partly transparent edges as well as obviously empty areas. Those edges can show a pale or dark outline after the conversion.
Where transparency is essential, keep a supported transparent format rather than trying to make JPEG do a job it cannot do. Converting a JPEG back to PNG will not cut out its background automatically. Background removal is an editing task and is not offered by these format converters.
Use size reduction with the destination in mind
The size-target tools attempt the selected threshold for supported images. Re-encoding and pixel reduction may be involved, so inspect the output’s actual dimensions and appearance. If a form also requires a minimum resolution, a small-enough download can still be unsuitable after its dimensions have been reduced.
Choose a target close to the real requirement with enough margin for rounded size labels and unit differences. The preset names use binary KiB or MiB thresholds. Do not pick 100 KB simply because it is the smallest option if the receiver permits a much larger image. Unnecessary reduction can discard detail without helping the task.
Screenshots need a readability check
A screenshot often contains flat colours and sharp text. Look closely at reference numbers, small punctuation and thin lines after changing its format or size. A preview scaled to fit a phone screen can conceal changes that become obvious when the recipient zooms in or reads the image on a larger display.
If you have access to the original document, a direct export may be more appropriate than a screenshot. A document saved as PDF can retain information that a picture of the screen does not. Follow the receiving format requirements and avoid placing a low-resolution screenshot inside another container just to make its extension look acceptable.
Orientation and cropping are different corrections
The orientation tool can normalise recognised JPEG orientation. PNG and WebP inputs currently return unchanged; use an editor if those pictures need a visual turn. It is useful when viewers disagree about which way a photo should face. It does not decide the correct horizon or provide arbitrary manual rotation controls, and it does not crop a picture into a required shape.
Check width and height after correcting orientation. A portrait picture can have the right number of pixels but the wrong shape for a wide banner. Stretching it to fill that space can distort the subject. Use a suitable source or a permitted crop in an editor when the receiving layout requires a different composition.
Metadata preparation is a separate choice
The metadata-removal tool creates a new image without copying source EXIF, GPS and comment information. It uses re-encoding rather than promising that the original image bytes remain untouched. The browser may add its own encoding information, so the output is not described as completely metadata-free.
Keep original photographs when capture information or an unchanged record matters. Also inspect visible details before sharing: removing source location fields does not conceal a street sign, address label or recognisable scene. If the picture needs redaction, use an appropriate editing workflow rather than treating metadata removal as an anonymity guarantee.
Plan for the size of the decoded image
The stored MB figure is only part of the browser workload. A compressed image can expand into millions of pixels when read. The image tools limit inputs to 25 MiB, and image re-encoding paths limit decoded pictures to 18 million pixels. An already-upright orientation result can return unchanged without decoding. A very large panorama may therefore be unsuitable even when its compressed file looks manageable.
If processing fails, read the message and try the relevant next step. A supported export from the source application may be necessary for an oversized or unusual image. Closing other heavy tabs can help with memory pressure, but it does not remove a format or pixel-budget limit. Do not keep submitting an unsupported file unchanged.
Review the image where it will actually be used
Open the downloaded copy and compare its important details with the original. Check the orientation, background, corners and smallest required text. For a product image, consider the actual listing background; for evidence, make sure all required content is still visible. The best review depends on the use of the picture.
Finally, measure the saved file against the receiving rules and select that exact copy in the upload field. A converter cannot sign into the receiving account, meet a hidden content policy or guarantee approval. If the technical requirements are satisfied but the upload still fails, examine the service instructions and session rather than damaging the image through repeated changes.
Check which version a phone has selected
A photo library can offer an edited copy, a shared copy or the original, and the thumbnail may not make the difference clear. Look at the file information and the source location when the converter reports an unexpected format or dimension. A small messaging attachment is not equivalent to the camera original.
If the result is unexpectedly blurry, first check that input choice before changing more settings. Obtaining the intended original can solve a quality problem that no format conversion can repair. After processing, save the output with a name that makes the delivery version easy to distinguish from the source.
Questions that come up
Should I always convert images to JPG for compatibility?
Only when JPEG fits the destination and the picture. Transparent graphics and text-heavy screenshots may need a different accepted format. Read the upload list and consider what must survive before converting. The most familiar extension is not automatically the most suitable choice.
Can these tools improve a blurry original?
They do not restore missing detail. A larger export or different format cannot recreate information that the source lacks. Find the original photo, rescan the document or export from the original application when the required details are unreadable.