About
Browser-first image tools
ImgLab exists because most image conversion happens at the worst possible moment — you need a 2MB JPEG of an iPhone photo for a school form, an Etsy listing, a passport application, or a contractor estimate, and the only tools that come up in search uploads your file to a remote server you have never heard of. ImgLab inverts that flow. Files stay on your device. The browser does the work. Nothing is sent to a server controlled by us because no server is involved.
The first cluster of tools focuses on what photographers and everyday iPhone users actually run into: HEIC to JPG (because iPhones default to HEIC since iOS 11 and most forms still expect JPEG), HEIC to PNG, PNG to WebP, a smart resizer with aspect-ratio lock, a quality-aware compressor that targets a file-size budget, and a favicon generator that emits the correct 16/32/180/192/512 pixel sizes for a modern manifest. Each tool is built around one conversion or transformation, with a result-first layout and no upsell.
How the processing actually works
Under the hood, ImgLab uses standard Web APIs — OffscreenCanvas, the Canvas 2D context, the WebP encoder built into recent versions of Chromium, Firefox, and Safari, and the WASM build of libheif for HEIC decoding. None of these require a network round-trip after the page has loaded. You can confirm it in the browser’s Network tab: open a tool, pick a file, run the conversion, and you will not see an upload to any imglab.tools origin.
Who maintains ImgLab
ImgLab is published by the inovisum team, a small tools studio that runs a portfolio of single-purpose utility sites. The codec list and the tool roster are reviewed each quarter; when a browser ships native support for a new format (AVIF encoding, for example), the corresponding converter is added in the next release pass. If a conversion you rely on is missing, write in and it will be triaged on the next maintenance pass.