Frontend & Mobile

Image, SVG & icon tools

Shipping an image usually means changing something about it first: converting it to a format the browser or platform actually wants, cropping it to a fixed size, stripping out the EXIF and GPS data a phone camera embedded by default, or turning one source image into the full set of favicon sizes a site needs. These tools handle those specific jobs directly on the file you already have.

The Image converter and Image resizer and cropper cover the everyday format and dimension changes across PNG, JPG, WebP and AVIF, the latter with a live crop preview. The SVG optimizer works on markup rather than pixels, formatting or minifying SVG and trimming metadata that inflates file size without changing how it renders. The Favicon generator turns one source image into favicon.ico, the PNG sizes browsers expect and a webmanifest, and the Image Metadata Viewer and Remover strips EXIF, GPS, camera and XMP data before you publish a photo.

5 tools

Images, SVG & Icons tools FAQ

Does removing EXIF data change how an image looks?

No, EXIF, GPS, camera and XMP data is metadata stored alongside the pixels, not part of the visible image, so stripping it leaves the picture unchanged. The Image Metadata Viewer and Remover lets you inspect that hidden data first and then remove it before you share or publish the file.

What image formats does a favicon actually need?

A modern favicon setup needs an .ico file for legacy support plus several PNG sizes and a webmanifest for home-screen icons, more than most people generate by hand. The Favicon generator produces favicon.ico, the PNG sizes and the webmanifest from a single source image.

Why optimize an SVG file instead of leaving it as exported?

Exported SVGs often carry editor metadata, unused IDs and unnecessary precision that add file size without changing the rendered shape. The SVG optimizer formats or minifies the markup and trims that metadata, which is a quick check before shipping an SVG to production.