A transparent area is not a white area
A transparent PNG logo can appear white around the edges in one viewer and dark in another because the viewer is showing whatever lies behind it. A checkerboard is usually the editor's transparency indicator, not a pattern stored in the logo. An opaque white rectangle, in contrast, is part of the actual picture.
JPG stores an opaque image. During conversion, transparent and partially transparent pixels have to be combined with a background colour. OneImageTool's PNG to JPG path uses white, including under soft shadows and antialiased edges. The downloaded JPG therefore has a white background even when the PNG originally had no background.
| What you see | What to check | Next step |
|---|---|---|
| White rectangle after JPG conversion | Whether the original PNG was transparent | Keep PNG or WebP if transparency is required |
| White area already in the PNG | Whether it is opaque image content | Changing formats alone will not remove it |
| Pale edge on a dark page | Whether edge pixels were blended with white | Return to the transparent original |
| Checkerboard in the exported image | Whether the pattern is actual pixels | Inspect the source rather than trusting the preview |
Convert to JPG when a white background is acceptable
This converter does not offer a background-colour picker. If you need a different solid colour, composite the original PNG onto that colour in an image editor before making the JPG. A quality slider changes the encoding trade-off; it does not restore an alpha channel.
- Keep the original PNG. Open PNG to JPG and choose that original file.
- Confirm that a white background is acceptable in the receiving app, document or upload form.
- Set quality and generate the result. Inspect the background, fine letters and translucent edges in the actual comparison.
- Download the JPG and place it on the intended page. Check the whole rectangle, not just the logo at its centre.
Keep the transparent original for dark or coloured pages
If the destination accepts transparent PNG, keeping that source may be enough. PNG to WebP is another option when the destination supports it, but inspect the actual exported file over both light and dark backgrounds. Small shadows and partially transparent edges deserve a closer look than a fully transparent corner.
Do not first flatten the image to JPG and then expect JPG to PNG to restore the transparent area. That conversion can store the white rectangle in a PNG, but it cannot identify which white pixels once belonged to the background and which belonged to the subject. Return to the original transparent file.
Why a larger quality setting does not fix a white halo
An edge pixel can contain both the subject colour and partial transparency. Compositing it onto white produces a lighter opaque pixel. If that image is later placed on a dark page, the light edge may become noticeable. Increasing JPG quality does not undo the earlier background blend.
Re-export from the original with the final background already chosen, or retain alpha transparency in a supported format. Inspect at the intended display size as well as a closer zoom. A screenshot of a logo on a white page is also already flattened; changing the screenshot's extension will not recover the logo's original alpha data.
Check transparency and file requirements separately
An upload form can require JPG even when a transparent logo would look better. In that case, prepare an acceptable solid background deliberately and verify the result in the form. If the form accepts PNG or WebP, compare transparency, readable edges, dimensions and actual bytes before deciding.
Keep a transparent master and make destination-specific copies from it. Use a separate size-target workflow if the form also has a byte limit; making the file small and choosing the correct background are different checks.