This article focuses on the practical office need for unifying image formats into WebP, introducing how to use HeSoft Doc Batch Tool to import multiple image formats from a folder and batch convert them into WebP format. The tutorial combines examples of pre-conversion files including AVIF, BMP, WEBP, PNG, JPEG, HEIC, and GIF, and the post-conversion results where all are .webp, to explain key steps such as function entry, file import, log verification, output destination settings, and result checking.
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 simultaneously, each file may represent an image, but the adaptation for different formats during uploading, previewing, archiving, and delivery is not entirely consistent. If the goal is to standardize them to 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 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 so that users can directly follow the steps after reading.
Applicable Scenario: Images in a Folder Need a Unified Format
When organizing materials, many teams first collect images into a single folder. However, as source materials increase, the number of extensions in the folder grows. For example, clients might send HEIC files, design software exports PNGs, historical archives contain BMPs, web downloads are JPEGs, and there are some new AVIF formats. By the time they need to be delivered to a website, system, or other colleagues, you realize the formats are not unified.
In this case, batch converting all images in the folder to WebP is a more efficient approach. It is suitable for website image optimization, content material organization, project file archiving, batch publishing of product images, mobile image adaptation, and other scenarios. Compared to opening image software one by one for export, batch processing tools can consolidate operations into one task.
If you frequently process image directories rather than occasionally convert one or two images, establishing a fixed workflow is highly valuable: first collect the originals, then batch import, uniformly convert to WebP, and finally check the output directory. The screenshots in this article precisely illustrate the key stages of this workflow.
Result Preview: Mixed Format Image Directory Before Processing
Before processing, the sample folder contained 7 image files: 1.avif, 2.bmp, 3.webp, 4.png, 5.jpeg, 6.heic, 7.gif. Their names are sequentially numbered, but the formats are all different. For subsequent batch uploading or unified archiving, this directory has not yet reached a standardized state.
As seen in the screenshot, besides common PNG, JPEG, and GIF, it also includes AVIF, HEIC, BMP, and one existing WEBP file. This indicates that this process is not a single format conversion, but a multi-format image unification to WebP. Such a requirement is very typical in actual work, especially when images come from different devices and different people.
Result Preview: All Become WebP After Processing
After the conversion is complete, the file extensions in the output directory all become .webp, displayed as 1.webp, 2.webp, 3.webp, 4.webp, 5.webp, 6.webp, 7.webp. The file count matches the pre-processing count, and the naming maintains the corresponding relationship, making verification easy.
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 over to development colleagues for use, it can reduce the format confirmation step. For highly repetitive image organization work, this batch conversion result can significantly improve efficiency.
Operation Step 1: Open the Image Tool Category
After launching HeSoft Doc Batch Tool , select Image Tools from the left navigation bar. As shown in the screenshot, the software title at the top displays as HeSoft Doc Batch Tool , version v1.23.0. The left category includes various office processing entries, with image-related tasks concentrated under Image Tools.
After entering Image Tools, the right side displays multiple image processing functions in card form. Users can choose the corresponding entry based on the target format. The goal here is to uniformly convert images to WebP, so you need to select Image to WEBP Conversion. In the screenshot, the 13th item, Image to WEBP Conversion, is highlighted, and there is prompt text explaining its function is to batch convert image files to WEBP format.
The expected result of this step is entering the WebP conversion task page. As long as the function is selected correctly, 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 Image to WEBP Conversion page, you can see buttons at the top: Add Files, Import Files from Folder, Clear, and More. For the requirement of uniformly converting folder images to WebP, it is recommended to prioritize using Import Files from Folder, as it can add the directory's images to the task list all at once, which is 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. Both methods aim to add the images to be converted into the software's processing list. The screenshot shows 7 files have been imported, and the path column shows these files are located in the D:\test directory, indicating this is a batch of images from the same folder.
After importing, the software automatically generates a table record. The table columns include Sequence Number, Name, Path, Extension, Creation Time, Modification Time, and Actions. For batch tasks, this table is very important; it acts as a confirmation checklist before processing.
Operation Step 3: Check the Import Results via the Table
Before formal processing, it is recommended to check the table information item by item. First, look at the record count; the bottom of the screenshot shows the total record count is 7, consistent with the 7 files in the sample folder. Second, 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 like avif, bmp, webp, png, jpeg, heic, gif.
If you find records for images that do not need converting have been mixed in, you can use the delete icon in the Actions column to remove that record. If the entire list was imported incorrectly, you can use the Clear button to start over. The advantage of this is that you can exclude erroneous files before batch processing, avoiding rework after 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 wish to unify all images and output them to a new 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 setting the 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, setting the save location 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, you only need to package the output directory for delivery.
Since the current screenshot does not show the specific button details of the save location page, the names of unexhibited 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 the save location is set, the workflow will enter Step 3, Start Processing. The software will perform the conversion for each image file based on the previously imported task list and output them in WebP format. After waiting for the process to complete, open the output directory you set and view the generated files.
According to the post-processing screenshot, this task ultimately generated 7 files from 1.webp to 7.webp. The file count matches the original record count, indicating a corresponding result was generated for each record. It is recommended at this point to open some images for spot-checking to confirm the image content is normal, especially whether the display effects after converting formats like HEIC, GIF, and AVIF meet your usage requirements.
Common Issues and Precautions
1. Will unnecessary files be imported when importing from a folder? This depends specifically on the software's recognition and the directory you choose. After importing, you must check the records via the table and delete 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 output is correspondingly 1.webp to 7.webp after conversion. If your file names are chaotic, it is recommended to organize them before conversion for easier subsequent verification.
3. Will the original images still need to be kept? It is recommended to keep them. 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, it is not recommended to keep only the conversion results.
4. Why set a separate output directory? A separate directory makes the results clearer and avoids mixing original images and WebP. For batch tasks with many files, a clear output directory can significantly reduce subsequent organizational work.
5. How to ensure nothing is missed when there are many images? After importing, check the total record count and compare it with the number of files in the original folder. After processing is complete, also check the file count in the output directory. Consistent counts before and after serve as an important basis for judging the completion of a batch conversion task.
Summary: Turning Image Format Conversion into a Reusable Batch Office Workflow
Unifying multiple image formats in a folder to WebP should not rely on manual, one-by-one processing. Using HeSoft Doc Batch Tool , you can consolidate the steps of importing, verifying, setting output, and starting processing, making it suitable for batch image organization work in daily office tasks.
If your material directories often mix formats like PNG, JPG, JPEG, BMP, HEIC, AVIF, GIF, you can follow the method in this article: open Image Tools, select Image to WEBP Conversion, 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 an image folder that needs organizing and complete a WebP batch conversion by following the steps.