What this checklist covers
This is practical guidance for the stated workflow. It does not replace checking the output for your own document and use case.
Choose from the visual requirement first
JPG is often useful for photographs because it can produce a compact file with acceptable visual loss. PNG is usually a better fit for screenshots, diagrams, line art, or images where crisp text and exact pixels matter. PNG and WebP can support transparency; JPG cannot.
If an image has transparent areas, converting it to JPG normally replaces those areas with a solid background. That can be fine for a photo but can break a logo, overlay, cut-out product image, or interface asset.
- Photographs without transparency: try JPG.
- Screenshots, diagrams, and sharp text: try PNG.
- Transparency with modern browser support: consider WebP or PNG.
Do not assume a format conversion makes a file smaller
The original encoding and image content matter. A simple graphic can already be extremely efficient as PNG, while converting it to JPG or WebP may increase its byte size. A detailed photograph can show the opposite result. Use the converted output size as the decision, not a format slogan.
Resizing has a different purpose from re-encoding. If an image is much larger than its displayed size, reducing its dimensions can save more bytes than changing the format alone.
- Compare original and output size after conversion.
- Resize oversized images before deciding that more compression is necessary.
- Keep the original when further editing or a higher-quality export may be needed.
Protect privacy separately from format choice
Image files can carry metadata such as camera or capture details. Changing the image format may alter or remove some metadata, but that is not a dependable privacy workflow. Use Remove Image Metadata when removing standard metadata is the purpose, then inspect the result for the information you care about.
Visible information is different from metadata. A name, address, face, or document number printed in the pixels will remain visible after metadata removal and requires a separate editing decision.
- Use Remove Image Metadata for standard metadata cleanup.
- Review visible pixels separately from hidden metadata.
- Keep the original if camera or capture metadata is important to retain.
Temporary processing and privacy
Image conversions and metadata-removal requests use temporary processing storage. A converted image is still a new file that should be reviewed before you publish or share it.
Read the Privacy Policy →Troubleshooting
My JPG has a white background
JPG does not support transparency. Use PNG or WebP if transparent areas must remain transparent.
The converted file is larger
The original may already be efficient for its content. Compare the outputs and keep the smaller usable file instead of converting repeatedly.
I removed metadata but sensitive text remains
Metadata removal does not alter the visible image content. Sensitive pixels need a separate editing or redaction workflow.
Editorial note
NetroDoc practical guides explain a specific file workflow and link to the tools that carry out each step. They avoid presenting a general recommendation as a guarantee for every file.