Resize Multiple

Purpose & User Intent: The tool solves batch resizing of image assets for web publishing, social media, thumbnails, and CMS pipelines. Assumption: The most common use case is batch resizing multiple images for web, social, and thumbnails. Target users include content teams, freelancers, and developers integrating asset pipelines. The tool is used before publishing or asset distribution to produce consistent, size-variant outputs from a single source set. Core Logic & Features: Core capabilities include batch scaling of image files to multiple target dimensions, aspect-ratio preservation, optional padding, and optional format conversion. Required features: input image list, array of target sizes, output path specification, and quality control. Advanced features (optional): automatic color-space conversion, cropping vs. letterboxing, and live naming conventions. Outputs include resized images with size suffixes. Inputs & Outputs: Inputs: files (list of images), sizes (array of {width, height}), output_format (e.g., JPEG, PNG, WebP), maintain_aspect (boolean), add_padding (boolean), quality (0-100). Outputs: resized_images (list of {filename, width, height, format, url}). Validation: width and height > 0, supported formats, at least one input file and one target size. Algorithms & Calculations: For each input image and each target size, compute target dimensions. If maintain_aspect is true, scale by min(target_w/width_in, target_h/height_in). If add_padding is true and aspect differs, compute canvas size and center the image. Encoding uses requested format with the given quality. Outputs are named with suffixes like _w800h600. Error & Edge Cases: Handle missing inputs, zero or negative dimensions, unsupported formats, decoding failures, and memory errors for very large batches. If an output file already exists, apply overwrite policy. External data unavailability is not expected. Industry/Region & Localization: Units are pixels; follow web image standards. Formatting respects common MIME types; no regional currency or locale data is required. Assumptions & Exclusions: Assumes inputs are accessible image files or binary streams; excludes UI styling, real-time preview, and editing beyond resizing. Upscaling outside safe limits is not performed unless explicitly requested.