Photoshop script for batch WebP and JPEG export

The challenge

Publishing a catalog involves repeated changes to size, quality, naming and product information for every image.

Preparing images for an online store starts before upload. Photographs of the same product need consistent sizing, preserved framing and filenames that help identify their content. When this preparation relies on repeated manual actions, small differences between files make the delivery harder to review.

This project organizes the routine inside Adobe Photoshop. The operator enters product details once and the script applies the workflow to saved documents already open in the application. The service can be tailored to the business: output formats, product fields, folder structure and information needed by the catalog.

How the workflow works

1. 01

   Enter product information

   A batch can receive details through a form, JSON file or generic configuration. The supplied title, category and other characteristics feed naming and metadata, without requiring the operator to repeat the same entry for every file.

2. 02

   Prepare working copies

   Processing uses duplicate documents and fits them within 2000 × 2000 pixels without upscaling smaller images. Square originals keep their framing; other aspect ratios can receive additional canvas space to create a square output.

3. 03

   Export the formats

   Outputs are organized into WebP and JPEG folders. A sequence of quality levels aims for a 700 KB target. If that target cannot be reached, the workflow retains the final dimensions and records a warning.

4. 04

   Review the delivery

   The report lists dimensions, quality, file size and warnings for each image. A separate JSON file organizes information that can support publishing. Sequential naming checks existing outputs in both formats before choosing the next filename.

The work

A JSX script collects batch details, prepares duplicates and delivers WebP, JPEG and supporting files for publishing.

• Batch WebP and JPEG export
• Dimension limit without upscaling smaller originals
• Metadata and per-file reporting

Metadata in context

XMP/IPTC information travels with the image, while the supporting file collects catalog data. This separation makes the delivery usable by an operator and available for a later system integration.

The publishing workflow still has to use these details. Writing a description into a file does not automatically insert an HTML alt attribute and does not guarantee visibility in search.

Explicit quality decisions

Pixel dimensions and file size are different requirements. The script avoids reducing dimensions further merely to achieve the file-size target, making that decision visible in the report.

Before delivering a customization, the review batch should include varied backgrounds, textures, aspect ratios and smaller originals. The client can then assess appearance and decide which warnings require attention.

Example of scaling without upscaling

Adapted example explaining the rule. It is not the complete script or a snippet independently validated in Photoshop.

function outputSize(width, height, limit) {
    var scale = Math.min(1, limit / Math.max(width, height));
    return {
        width: Math.max(1, Math.round(width * scale)),
        height: Math.max(1, Math.round(height * scale))
    };
}
var size = outputSize(2400, 1600, 2000);
// Export uses a duplicate document.
// The report records dimensions and warnings.

Delivery and context

The implemented workflow includes form or JSON input, export and reporting. Visual review of the final Photoshop version remains part of acceptance.

Frequently asked questions