Convert a folder without turning it into a grading project
Batch Converter is the larger-folder conversion workflow in PRVKIT. Choose local files or a folder, define an output recipe and export the accepted results. It is useful when a delivery contains mixed image formats, oversized dimensions or inconsistent names. It does not apply Studio LUTs or ask you to assemble a client welcome document. Import, Output and Export remain the three practical stages.
For example, a photographer may need JPEG copies of a structured folder of finished PNG images. A designer may need WebP versions of product photographs while preserving relative subfolders. The converter keeps those tasks focused on representation, dimensions and organization. Originals remain untouched, so the converted collection can be evaluated before it replaces any delivery workflow.
Read the import summary before committing to a recipe
Supported still-image inputs include JPEG, PNG, WebP, AVIF, GIF, BMP, single-page TIFF and browser-native HEIC/HEIF. A recognized extension is not enough: actual format inspection and decoder support determine admission. Animated files and multipage containers have narrower handling or are skipped rather than silently representing an entire sequence or document with one image.
Configured selection admission permits 2,000 files and 20 GiB of source bytes. Individual sources are capped at 250 MiB; the processing tier is 64 megapixels and 16,000 pixels per edge, with finite format and active-memory checks. These independent limits are not a combined workload promise. A compressed photograph may require several much larger working buffers when decoded, resized and encoded.
Preflight inspects sources serially and records supported properties, relative paths and reasons for skipped items. Read those reasons instead of assuming that every selected file will produce an output. A source can be within the selection allowance but unsuitable for a particular encoder or destination. Folder selection and direct output-folder writing also depend on browser APIs and explicit user permission.
Choose a format for the recipient
JPEG suits photographic copies when transparency is unnecessary and the receiving application expects a familiar still-image file. Its quality control trades encoded bytes against visible changes. Check gradients, hair, fine texture and lettering rather than relying on a particular percentage. A JPEG re-export is another encoding generation, even when the source was already JPEG.
PNG preserves the decoded pixel grid without a lossy quality setting and supports transparency. That does not mean it preserves the original file's bytes, metadata, profile or high-depth representation. A photograph saved as PNG can be considerably larger than its JPEG source. Use it when the requested pixel or alpha behavior justifies the storage and transfer cost.
WebP export uses the reviewed local encoder rather than assuming that every browser can encode it natively. AVIF output is available only when the browser supports the required encoding path. Do not rename a PNG or JPEG extension to claim a different format. Read the reported output type and open a real sample in the recipient's application before processing the whole job.
HEIC support here is a native-browser path. The dedicated shared HEIC tools and Studio have different decoder arrangements, so their ability to decode a particular source does not establish Converter compatibility. Convert one permitted sample through the appropriate tool when you need to assess that boundary.
Set dimensions and naming deliberately
Choose whether to keep dimensions or apply the available resizing recipe. Reducing the long edge can save more space than forcing a large photograph through a very low quality setting. Upscaling adds pixels, not missing source detail. Check a small representative export at the actual viewing size, especially when text or fine product edges are important.
Keep the naming rule understandable. A stable prefix and sequential number can help a recipient navigate a collection, while preserved source names may be better for traceability. Review the naming preview and relative folders before exporting. Collision handling protects existing output names, but it does not decide whether two similarly named photographs are duplicates or which one you intended to deliver.
Folder structure reflects the selected relative paths, not unrestricted access to your disk. The tool does not need to upload a directory tree to process its images. Keep an independent source folder, choose a deliberate output destination and avoid assuming that a browser-selected folder is a backup of the originals.
Pick a destination your browser can finish
A supporting browser can write results into an approved local folder one image at a time. A streamed ZIP path is capped at 1 GiB. Where direct streaming is unavailable, independent ZIP parts are bounded at 128 MiB each and require explicit download/continue steps. The next part is not accumulated indefinitely alongside every completed part.
An encoded result must fit the selected destination. If it cannot, choose a supported direct-folder path or deliberately reduce dimensions or quality. The converter does not quietly discard detail to satisfy a ZIP limit. A group of small files and one huge high-resolution image stress different parts of the pipeline; successfully selecting both says little about the final archive size.
Pause and cancel are controls over ongoing work, not proof that a native codec stopped instantly. Let the current operation settle before retrying. Review the completion receipt, failed items and retained successful results. Retry in the same session uses the captured job settings rather than guessing what a changed control should mean for an earlier file.
Access, privacy and checking the delivery
Conversion export requires monthly PRO. The Studio Day Pass does not unlock Batch Converter. For a small Free resize/compression job of up to twenty supported images, use the separate Batch Image Optimizer. For a shared photographic grade, use Studio. Neither alternative changes this tool's access policy.
Selected creative bytes and paths stay in the browser processing workflow, while application resources still load from the site. Account verification and billing are separate services; signing in restores verified access without uploading creative files. Local processing is not a promise of no network requests or permanent automatic job recovery.
Open the saved output folder or each downloaded ZIP part. Check counts, names, relative paths, actual formats, dimensions and a few difficult images. A download starting is not proof that the browser finished saving it. Keep the originals until the recipient's needs and your own checks are satisfied.