This article focuses on the practical office need to unify image formats to WebP, and explains how to use HeSoft Doc Batch Tool to import various images from a folder and batch convert them to WebP format. The tutorial uses before-and-after examples—input files including AVIF, BMP, WEBP, PNG, JPEG, HEIC, GIF, and output files all as .webp—to walk through key steps such as accessing the function, importing files, verifying records, setting the save location, and checking the processing results.
In enterprise office work, content management, and project delivery, the more varied the image formats in a folder, the more troublesome subsequent use becomes. For example, if an image directory contains AVIF, BMP, WEBP, PNG, JPEG, HEIC, and GIF, each file represents an image, but the adaptability of different formats for uploading, previewing, archiving, and delivery is not entirely consistent. If the goal is to unify them into WebP, manual conversion becomes repetitive labor.
This article will use HeSoft Doc Batch Tool as an example to explain how to batch convert multiple image formats to WebP by importing images from a folder. HeSoft Doc Batch Tool is a batch file processing software designed for office scenarios, suitable for standardizing and streamlining a large number of repetitive file operations. This article focuses on batch image processing, enabling users to follow the steps directly after reading.
Applicable Scenario: Images in a Folder Need a Unified Format
Many teams first collect images into a single folder when organizing materials. However, as sources increase, the number of file extensions in the folder grows. For instance, clients send HEIC files, design software exports PNGs, historical archives contain BMPs, web downloads are JPEGs, and there are some newer AVIF formats. The inconsistency in format only becomes apparent when the time comes to deliver to websites, systems, or other colleagues.
In such cases, batch converting all images in the folder to WebP is a more efficient processing method. It is suitable for scenarios such as website image optimization, content material organization, project file archiving, batch product image publishing, and mobile image adaptation. Compared to opening images individually in software and exporting them, a batch processing tool can consolidate operations into a single task.
If you frequently handle image directories rather than converting just a couple of images occasionally, establishing a fixed workflow is highly valuable: collect the original images, import them in batch, uniformly convert to WebP, and finally check the output directory. The screenshots in this article perfectly illustrate the key stages of this workflow.
Result Preview: Before Processing, a Mixed-Format Image Directory
Before processing, the example folder contains 7 image files: 1.avif, 2.bmp, 3.webp, 4.png, 5.jpeg, 6.heic, 7.gif. Their names are numbered consecutively, but their formats vary. This directory has not yet reached a standardized state for subsequent batch uploading or unified archiving.
As seen from the screenshot, besides common formats like PNG, JPEG, and GIF, it also includes AVIF, HEIC, BMP, and an existing WEBP file. This indicates that this processing task is not a single format conversion but a unification of multi-format images into WebP. Such a requirement is very common in actual work, especially when images come from different devices and personnel.
Result Preview: After Processing, All Become WebP
After the conversion is complete, all file extensions in the output directory become .webp, displayed as 1.webp, 2.webp, 3.webp, 4.webp, 5.webp, 6.webp, 7.webp. The number of files is consistent with before processing, and the naming maintains a corresponding relationship, facilitating verification.
After unifying to WebP, the directory structure is cleaner, and subsequent delivery is clearer. Whether uploading to a website backend, syncing to a project resource library, or handing it over to a developer colleague for use, it reduces the need for format confirmation. For highly repetitive image sorting tasks, this batch conversion result significantly improves efficiency.
Operation Step 1: Open the Image Tool Category
After launching HeSoft Doc Batch Tool , select Image Tools in the left navigation. The screenshot shows the software name at the top as HeSoft Doc Batch Tool , version v1.23.0. The left category includes various office processing entries, with image-related tasks grouped under Image Tools.
After entering Image Tools, the right side displays multiple image processing functions in card format. Users can select the corresponding entry based on the target format. The goal this time is to convert images uniformly to WebP, so you need to select Convert Image to WEBP. In the screenshot, the 13th item, Convert Image to WEBP, is highlighted, with descriptive text indicating its function is to batch convert image files to WEBP format.
The expected result of this step is to enter the WebP conversion task page. As long as the correct function is selected, subsequently imported images will be processed according to the rules of this task, without the user needing to set conversion methods for each original format individually.
Operation Step 2: Use Add Files or Import Files from Folder
After entering the Convert Image to WEBP page, you can see Add Files, Import Files from Folder, Clear, and More buttons at the top. For the need to uniformly convert folder images to WebP, it is recommended to prioritize using Import Files from Folder, as it can add all images from the directory to the task list at once, suitable for batch processing.
If you only need to process a small number of images scattered in different locations, you can also use Add Files. The purpose of both methods is to add the images to be converted to the software’s processing list. The screenshot shows that 7 files have been imported, and the path column indicates these files are located in the D:\test directory, confirming they are a batch of images from the same folder.
After importing, the software automatically generates a table record. The table columns include Index, Name, Path, Extension, Creation Time, Modification Time, and Actions. For batch tasks, this table is very important; it serves as a confirmation checklist before processing.
Operation Step 3: Check the Import Results via the Table
Before formally processing, it is recommended to inspect the table information item by item. First, check the record count; the bottom of the screenshot shows a total record count of 7, consistent with the 7 files in the example folder. Next, check the Name column to confirm these are the images you need to process this time. Then, check the Extension column to confirm it includes the expected formats such as avif, bmp, webp, png, jpeg, heic, gif.
If you find records mixed in that do not need conversion, you can use the delete icon in the Actions column to remove that record. If the entire list is imported incorrectly, you can use the Clear button to start over. The advantage of doing this is that you can exclude incorrect files before batch processing, avoiding rework after the processing is complete.
In this example, 3.webp is already in WebP format. Whether to keep it depends on your actual goal. If you only want to convert non-WebP images to WebP, you can delete the existing WebP; if you want to unify all images into a new output directory, you can keep it.
Operation Step 4: Click Next to Enter Save Location Settings
After confirming the pending records are correct, click the Next button at the bottom of the page. The workflow prompt at the top of the interface shows that Step 2 is Set Save Location. The purpose of this step is to determine which directory the converted WebP images will be saved to.
In batch file processing tasks, the save location setting is very critical. It is recommended to specify a separate output directory for the resulting files and not mix them directly with the original files. Doing so has at least three benefits: first, it facilitates comparison before and after processing; second, it avoids accidental deletion or misuse of original images; third, for delivery, you only need to package the output directory.
Since the current screenshot does not show the specific button details of the save location page, the names of undisplayed controls are not described here. In actual operation, follow the interface prompts to select or set the save location, then proceed to the next step.
Operation Step 5: Start Batch Processing and View WebP Output
After completing the save location settings, the process will enter Step 3, Start Processing. The software will execute the conversion for each image file based on the previously imported task list and output them in WebP format. After waiting for the processing to finish, open your designated output directory to view the generated files.
According to the post-processing screenshot, this task ultimately generated 7 files, from 1.webp to 7.webp. The number of files matches the original record count, indicating that each record generated a corresponding result. It is advisable to open some images for spot-checking to confirm the image content is normal, especially whether the display quality of converted formats like HEIC, GIF, and AVIF meets your usage requirements.
Common Issues and Precautions
1. Will unnecessary files be imported when importing from a folder? It depends on the software's recognition and the directory you select. After importing, be sure to check the records in the table and delete any unnecessary entries if needed.
2. Do I need to organize file names before conversion? Not necessarily. In the example, the original file names are 1 to 7, and the outputs are correspondingly 1.webp to 7.webp after conversion. If your file names are messy, it is recommended to organize the naming before conversion to facilitate subsequent verification.
3. Will the original images still need to be retained? Retention is recommended. WebP files are suitable for publishing and delivery, while original images are suitable for backup and further editing. Especially for client materials, design source files, and important project images, keeping only the conversion results is not advisable.
4. Why set a separate output directory? A separate directory makes the results clearer, avoiding mixing original images with WebP files. Once a batch task involves many files, a clear output directory can reduce a lot of subsequent sorting work.
5. How to ensure none are missed when the number of images is large? After importing, check the total record count and compare it with the number in the original folder. After processing is complete, also check the file count in the output directory. Consistent counts before and after are an important basis for judging the completion of a batch conversion task.
Summary: Turn Image Format Conversion into a Reusable Batch Office Workflow
Unifying multiple image formats in a folder into WebP should not rely on manual, one-by-one processing. With HeSoft Doc Batch Tool , steps including importing, verification, output setting, and starting processing can be centralized, suitable for routine image batch sorting tasks in daily office work.
If your material directories often mix formats like PNG, JPG, JPEG, BMP, HEIC, AVIF, GIF, etc., you can follow the method in this article: open Image Tools, select Convert Image to WEBP, import images from the folder, check the task list, set the save location, and then start batch processing. This not only saves time but also makes image delivery more standardized and stable. You can now select a folder that needs sorting and complete a WebP batch conversion by following the steps.