Upload one source image
Start with a static JPEG, PNG, or WebP. The app checks the file size and image limits before creating a temporary processing job.
How it works
The product is intentionally narrow: upload one static source, configure the image pack, let the worker generate responsive assets, then download the result before temporary files expire.
Start with a static JPEG, PNG, or WebP. The app checks the file size and image limits before creating a temporary processing job.
The backend reads dimensions, format, transparency, aspect ratio, and image characteristics. This gives the configure screen enough context to suggest practical defaults.
Choose output formats, responsive widths, quality levels, image role, loading behavior, and code preferences. Defaults are selected, but every important choice remains visible.
A worker process uses pyvips to generate optimized variants while the web UI tracks job progress. The API stays responsive because CPU-heavy conversion does not run in the request handler.
The result includes generated images, a manifest, examples for common implementation targets, and a ZIP package for downloading the complete image pack.
Source files and generated outputs are stored privately and removed after the retention window. The MVP is built for temporary conversion, not permanent asset hosting.
Image conversion can be slow and memory-heavy. Splitting the work into upload, analysis, configuration, background processing, and packaging keeps the API responsive and makes recovery clearer when a job fails.
See what is planned next →