What is Image Resizing?
Image resizing changes the pixel dimensions of a picture — its width and height — without altering the underlying file format. A 4000x3000 photo from your phone contains twelve million pixels. Display it in a 400x300 thumbnail on a product page and the browser still has to download all twelve million pixels, decode them, and then scale them down on the fly. That wastes bandwidth, slows rendering, and drains battery on mobile devices. Resizing ahead of time gives you an image that matches its display context exactly, so every pixel in the file earns its keep.
Pixel dimensions and DPI are two different things, and confusing them causes trouble. Pixel dimensions describe the actual grid of color data — 1920 pixels wide by 1080 pixels tall, for example. DPI — dots per inch — only matters when the image is printed on paper. A 300 DPI setting tells a printer to pack 300 pixels into every physical inch. On screen, DPI is irrelevant because monitors have fixed pixel grids. A 1920x1080 image displays identically whether its metadata says 72 DPI or 300 DPI. When you resize for the web, focus entirely on pixel dimensions. When you resize for print, multiply the desired physical size in inches by the target DPI to get the pixel dimensions you need. A 4x6 inch print at 300 DPI requires 1200x1800 pixels.
This tool resizes your images entirely inside your browser using the Canvas API drawImage() method. You pick a target width or height, the tool calculates the other dimension to preserve the aspect ratio, and then it redraws the image onto a canvas of the new size. Nothing gets uploaded to any server. Your files stay on your machine from start to finish, which matters when you are working with client photos, proprietary mockups, or anything else you would rather not send across the internet.