Pixel Art Resizer

Purpose & User Intent: The Pixel Art Resizer is a domain-focused image processing tool used to resize pixel art assets for games, icons, and sprites. Intended users include solo developers, asset shops, artists, and toolchains that require predictable scaling. Typical use cases include upscaling 8x8 sprites to 32x32, converting a limited palette spritesheet to a larger canvas, or preparing assets for multiple platform resolutions while preserving hard edges. Core Logic & Features: It performs palette-aware, nearest-neighbor resizing by default to keep crisp pixels. Optional methods such as bilinear or bicubic are available for non-pixel art. Batch processing enables queuing multiple images with consistent settings. Two input modes exist: specify target width/height or a single scale factor. The tool preserves transparency, supports indexed outputs (PNG-8) with optional dithering, and validates inputs (positive dimensions, non-zero scale). When a palette is provided, color remapping occurs during output generation and respects the chosen format. Inputs & Outputs: Inputs include input_image (file, required), width (pixels, optional), height (pixels, optional), scale_factor (float, optional), preserve_aspect (bool, default true), method (string enum), output_format (string enum), dithering (0-100, optional), color_palette (array of hex colors, optional). Outputs include output_image (file), width_out (px), height_out (px), final_palette (array, if palette-reduced), estimated_file_size (bytes). Algorithms & Calculations: If scale_factor > 0, width_out = round(width_in * scale_factor) and height_out = round(height_in * scale_factor) when preserve_aspect is true; otherwise explicit width_out/height_out are used. If output_format is indexed, input colors map to the nearest palette colors with optional dithering. Otherwise, resize uses full color depth. Non-integer results are rounded; negative values are rejected. Error & Edge Cases: Unsupported input formats trigger errors; large dimensions exceed limits, or missing required inputs trigger errors. Animated inputs require per-frame processing or conversion to still frames. Palette reductions may increase file size if dithering is avoided; report any degradation in quality. Industry/Region & Localization: Pixel measurements use pixels; color space is typically sRGB; outputs align with game-art pipelines; no locale-specific formatting required. Assumptions & Exclusions: Assumes static, non-animated inputs unless frames are provided; does not perform perceptual color management beyond palette remapping; external UI styling or backend integration specifics are outside scope.