How to Batch Convert JPG, PNG and WebP Without Overwriting Files
Convert a mixed folder of images, preserve transparency where needed, avoid filename collisions and check the ZIP before a client handoff.

Convert a whole folder in one pass
Choose one destination format, select the images that need it, and download the converted copies together. That is the fastest way to turn a mixed JPG, PNG and WebP folder into a usable delivery. The main decision happens before uploading anything to the destination. Find out what the recipient accepts and what needs to survive conversion. A folder of product photos and transparent logos can contain valid images with very different requirements.
The Batch Image Converter accepts up to 20 images with a combined limit of 40 MB. Choose JPG, PNG or WebP, process the selection, and download the ZIP. A single result downloads as an image. The homepage converter can also handle a mixed selection. The dedicated tool gives you explicit JPG and WebP quality choices. Keep the original folder and save the result to a separate location.
Suppose a small shop needs twelve product photos and one transparent badge for a catalog upload. The catalog accepts JPGs for photos but asks for a PNG badge. Put the photos in the first batch and convert them to JPG. Export the badge separately as PNG so that its transparent areas survive. One delivery can contain multiple batches. Grouping files by their destination requirements saves more time than forcing everything into a single format.
Write down what the destination actually needs
Specifications can include pixel width, height, filename rules, file size per image and a limit for the whole upload. Ask whether the longest side is limited or both dimensions have to match an exact rectangle. A converter changes file format at the current dimensions. It cannot fix a 4,000-pixel photo for a form that caps uploads at 1,600 pixels. Use an Image Resizer for dimensions and run the format conversion afterward if necessary.
Inspect two or three representative originals. Note the dimensions, file type and approximate size of each. Include one photo, a screenshot with small text, and a transparent graphic if your set has all three. These are the samples most likely to expose a bad decision early. A background photograph often looks fine after compression. Price labels or screenshots can show visibly softer fine print at settings that look acceptable on the photo.
For a client handoff, put the destination in the folder name, such as marketplace-jpg or press-kit-png. Keep a small record of the chosen quality and pixel limits. If you need to redo two files next week, you can recreate the delivery without comparing fifteen differently named archives. The record can be a line in a text file. The useful part is knowing which source folder, output format and quality you used.
Pick JPG, PNG or WebP for a reason
JPG suits most photographic deliveries. It is widely accepted and gives you a quality setting. Converting to JPG fills transparent areas with white. A transparent black logo and a transparent white logo can behave very differently after that background change. Inspect logos at the intended background color before committing.
PNG suits transparency, diagrams and crisp edges. PNG uses lossless encoding, so it preserves the decoded pixels as it saves the new file. A PNG made from a JPG still contains any defects that were in the decoded JPG. It can also be much bigger. PNG makes sense where transparency or lossless re-encoding matters, especially for graphics and screenshots with narrow lines.
WebP suits web publishing when the destination handles it. WebP can support transparency and save photographic images efficiently. Confirm support wherever the image will travel. A content management system may accept WebP while an older print workflow rejects it. Test a real upload instead of assuming that because a browser can open a format, every destination accepts it. MDN image format guide
A useful tie-breaker is to export a pilot image in both plausible choices. Compare them at normal viewing size and enlarged where edge quality matters. Then compare file sizes. If a partner requested JPG and your WebP is a little smaller, the requested file type still decides the delivery. Where you control both the site and image pipeline, the answer can be different.
Prepare the batch and avoid duplicate-name surprises
1. Copy the selected source images into an input folder or use a dedicated view in your file manager.
2. Build a small pilot set and choose the output format before converting the whole selection.
3. Create a fresh output folder and put the downloaded ZIP there before extraction.
4. Count the extracted results and open a few from different parts of the batch.
5. Check that the final filenames match whatever the destination expects.
A common collision comes from banner.png and banner.webp entering the same batch. Both would normally turn into banner.jpg. FixHubLab adds a numeric suffix to keep both files. Capitalization also matters because a Mac, Windows PC or server may compare names differently. Distinguish important source files by design, such as banner-wide and banner-square, before conversion. A numeric suffix preserves the copies, while a meaningful source name tells the recipient which one to use.
Sometimes two files have different names but refer to the same listing. For example, IMG_1084 and front-new may both show a red mug from the front. The converter does not choose the better photo. If the destination needs one front photo, pick one before batching. For repeat work, a stable naming scheme such as sku-red-mug-front can help link the right image to the right item.
Run a pilot in the actual destination
Pick three files that matter. A low-detail photo tests compression in an easy case. A complicated image with fabric, grass or hair tests fine texture. A screenshot or logo tests edge quality. Export the files, unpack the result, and try the actual destination. Upload to a draft listing or a test folder when one is available. Confirm which files pass, whether the destination recompresses them, and how they look in the final layout.
Imagine a portal asks for JPGs under 2 MB. Your pilot exports are 320 KB, 710 KB and 2.3 MB. The first two files meet the limit. Open the third at full size and examine its dimensions. Lower JPG quality by one preset if the dimensions are required and there is still room to reduce quality. If the dimensions are far beyond what the portal displays, resize it and export again. Re-encode from the source every time so earlier compression artifacts do not accumulate.
A second pilot can verify that the proposed naming scheme works. Create a small set with a short filename and a longer one that contains spaces. If a downstream importer renames or rejects either, fix the rule ahead of the batch. Use Batch File Renamer to prepare copies where a prefix, numbering sequence or extension handling will help. Keep a small mapping if external records already point at the old filenames.
When your batch is bigger than the limits
Split the inputs into sets that fit the tool. The count limit and combined size limit apply independently. Ten images at 5 MB each exceed 40 MB even though the count is fine. A set of 21 small images exceeds the count limit even if all files together fit comfortably under the size cap. Make folder names such as photos-01 and photos-02, then extract each ZIP to its own output folder.
For large originals, reduce dimensions first if the destination does not need them. This has two benefits. It can reduce the source file size and the amount of decoded image memory needed. A compressed image can look small in the file manager but take many megabytes when decoded as pixels. Older phones and laptops can have less room for several large images or a result archive. When a batch fails midway, a smaller batch or a lower output resolution can help identify the file causing pressure.
Try to keep the designated input files together. If one image is too big or corrupt, separate it from the rest and run the working portion first. Fix the problematic file on its own. Only merge the delivery folders after you know the names cannot collide. When two batches open with an identical filename, extraction into the same folder can trigger an overwrite prompt. Review the conflict rather than applying the same choice to every file.
Four realistic delivery examples
Product photography for an online shop
A seller has several angles of each item, and their storefront crops all previews to the same square. They should select the layout or crop before conversion. Batch conversion preserves a portrait photo as a portrait photo. If the front face of a product is close to one edge, the storefront preview may cut it off. Check the draft listing with the first item and change the crop if needed. Then export the remaining photos with consistent padding and JPG or WebP as the store accepts.
Screenshots going into an instruction manual
Suppose a writer collects ten interface screenshots for a training handout. PNG is a strong starting point because small labels and thin borders need to be easy to read. Crop away irrelevant areas before conversion. If a screenshot shows a person’s name, account identifier or private notification, cover the information before export. Use the Screenshot Privacy Cleaner where needed. Changing format cannot remove information visible in the pixels.
Website thumbnails for a post archive
A website editor has older thumbnails in a mixture of formats and sizes. First establish the card aspect ratio and choose a crop per image so the subject remains clear. Export pilot WebP and JPG copies to check relative size and downstream support. If the site already serves modern formats with a fallback, use a set of each from the same crops. Preview the archive on a small screen and a desktop screen so titles and avatars inside images are still discernible.
An archive delivery to a client
A photographer delivers lightweight previews and keeps high-resolution originals in a separate archive. Preview copies can use JPG at a suitable quality. The original archive stays in the source format and should not inadvertently be replaced by the previews. Label the output folder review-jpg and share it separately. If the client picks only a few photos, produce final copies from the originals and keep naming consistent with the preview identifiers.
Troubleshoot the wrong result
A result looks blurry. Check the source at the same zoom level as the result. If the blur begins in the original, selecting PNG will preserve that blur. If the source is sharp but the JPG copy is softer, try a higher quality setting. When a web page displays a tiny thumbnail, a crisp large original and a blurry thumbnail can also be caused by the page stretching a smaller image.
The files are in a ZIP. Extract the archive with your file manager, then select the files in the extracted folder when you upload them elsewhere. A photo uploader typically wants the pictures inside. Check whether the receiver asks for the ZIP or separate files to avoid an unnecessary extra step.
An image keeps getting rejected. Confirm that its actual encoded format matches the extension and that it is one of the supported inputs. If it is an iPhone original ending in HEIC, use HEIC to JPG. If it ends in AVIF, try AVIF to JPG. Renaming the suffix alone leaves the file contents unchanged. Re-export the image through the right converter and open the result.
The ZIP is unexpectedly large. Compare the size of a few individual results with their input files. PNG output can be larger for an already compressed photo, and a batch inherits the size of every output. Try a photo-friendly output plus a lower preset where allowed. Check the destination’s limits before opening the smallest possible quality setting for every image.
A repeatable checklist for delivery day
Verify how many original files you intended to deliver, and compare it with how many extracted outputs you see. Open at least a few of the outputs themselves instead of relying on the previews in your source folder. Check the extension, dimensions, visual quality and file size. Where transparency matters, view the file on both light and dark backgrounds. A transparent graphic can look acceptable on white while failing on dark backgrounds if it has a white fringe from an earlier edit.
If folder order matters, sort by name and inspect the first, middle and last entries. A sequence with 1, 2 and 10 can sort as 1, 10, 2 depending on the software. Prefix digits with zeros when you control the names. Check the archive extraction once before sending it. That catches missing files or a naming rule the recipient’s system handles differently.
Finally, compare a compressed photo with the version that will actually be used. A crop or zoom in the web layout may expose details that looked fine when viewed as a thumbnail. If you revise a few items, regenerate them from the original folder and replace only those delivered copies after verifying their names. Keep the source material and approved exports in distinct locations. That simple split makes batch work repeatable when a client requests new dimensions or a platform changes its required format.
Make the process repeatable for a team
A team does not need a long instruction manual. Give the person receiving the images a sample they can compare against. A good reference set contains an accepted file, a typical rejected file, and the destination's current limits. Keep the examples in a folder that should never be included in a real shipment. If somebody else needs to run the batch, they can start with the accepted file and confirm that their output meets the same rules.
Before a large conversion, maintain a short list of exceptions. The logo with transparency, the panorama that needs a custom crop, and the illustration with important fine lines may each need a separate export. In a real delivery, those files are often more important than the routine images. Write down who checks them. Once they pass, use the batch tool on the ordinary group and add the exceptions to the finished folder under clear names.
If you work with several clients or portals, keep independent presets in your instructions. A news site might accept lightweight WebP while a printing supplier wants a high-quality JPG at specified dimensions. The instructions should name the recipient and describe the size or format that was tested there. A screenshot showing an upload confirmation can be evidence that the rule worked that day. Review the same test when a partner updates their portal.
Time yourself once during a normal delivery. Note how long you spent selecting files, converting, extracting and checking the results. If the export takes seconds and finding the correct source files takes fifteen minutes, improving folder structure helps more than changing the converter. If files get rejected after upload, the pilot should include the destination. These observations make the next batch faster because they show where the repeat work actually occurs.
If two destinations need different formats, do a separate quality check for each. An accepted shop image can still produce a poor print preview or a giant archive. A short note linking the file to its intended use will help someone choose the right version later.
