Why MyImgLite exists
Preparing images is often repetitive rather than complicated. A product catalog may need one width, an article library may need lighter cover images, and a shared folder may need a more widely supported format. Doing that file by file wastes time and makes output inconsistent.
MyImgLite provides focused tools for those repeatable jobs. Each page is built around one clear task, with shared settings for the full batch and a single ZIP download when the work is complete.
What the tools can do
The current workspace supports browser-decodable source images and exports JPEG, PNG, WebP, or AVIF. The available controls change according to the selected task and output format.
- Compress a batch with one output format and quality setting.
- Resize proportionally within a width or height without stretching the original composition.
- Set exact output dimensions when a CMS, marketplace, or template requires a fixed canvas.
- Convert supported images to JPEG, PNG, WebP, or AVIF and download individual results or one ZIP.
How local browser processing works
When you choose images, the application decodes, resizes, and encodes them in your browser using WebAssembly and web workers. The selected image files are not sent to an application server for conversion or storage.
Local processing removes upload and download queues, but it also means performance depends on the browser, available memory, source-image dimensions, output format, and batch size. AVIF output and very large source images can take longer than lighter JPEG or WebP work.
Choosing an output format
The right format depends on where the image will be used. MyImgLite keeps format selection explicit so you can make that tradeoff for each batch.
- JPEG is a practical choice for photographs and systems where broad compatibility matters.
- PNG is useful for transparency, screenshots, interface graphics, and lossless output.
- WebP offers a strong balance of quality, file size, transparency support, and modern browser compatibility.
- AVIF can produce smaller modern web assets, but support at the destination and longer encoding time should be considered.
Workflows the product is designed for
The tools are intended for practical preparation work rather than creative editing or cloud asset management.
- Standardizing product images before a catalog or marketplace upload.
- Preparing article covers, thumbnails, documentation screenshots, and campaign assets for the web.
- Creating lighter copies of event photos for delivery, email, shared folders, or archives.
- Converting a folder to the format required by a CMS, design handoff, or publishing workflow.
Batch limits and reliability
A batch can contain up to 30 images, each source file can be up to 100 MB, and the combined batch can be up to 512 MB. Resize dimensions accept whole-pixel values from 1 to 32,768.
Large decoded images can use substantially more memory than their compressed file size suggests. On a device with limited memory, smaller batches are more reliable. Results remain in the current browser session, so completed files should be downloaded before the page is closed or left.
Current scope and support
MyImgLite is not a cloud storage service, shared workspace, or user-account platform. It does not keep a server-side image library or recover files removed from your device. The original files are not changed; the browser creates new output files for you to download.
Questions, supported-workflow problems, and product feedback can be sent to [email protected]. A browser version, operating system, input format, selected output, and a description of the result are usually enough to begin investigating without sending a private image.