Guide
Read practical guides for local browser processing, local-first workflows, format choices, and privacy verification.
Read practical guides for local browser processing, local-first workflows, format choices, and privacy verification.
Open the page that matches your decision, then use the linked tool only when the limitations fit your file and workflow.
These guides split into two common starting points. Pick the one that matches why you are here, then branch into the theme sections below for more depth.
Read What WebP is first if you are not sure what the format actually changes. Then open Convert JPG to WebP Without Upload or Convert WebP Without Upload, depending on which direction you are converting. If you plan to convert a large batch, How browser-based processing works explains the processing boundary before you commit a big folder to it.
Start with What is EXIF data? to see what a photo can actually carry. Does social media strip metadata? and Does screenshotting remove metadata? cover two common assumptions worth checking before you rely on them. Remove Image Metadata Without Upload is the removal guide itself, and Remove location data from your photos covers device-level settings alongside the browser-based option.
These guides cover choosing and converting between WebP, JPG, and PNG.
Explains what the WebP format is, why browsers and sites adopted it, and where it still falls short of JPG or PNG for a given use case. Read this first if you are comparing formats before choosing an output for the Image Converter or either format-pair guide below.
Covers converting a WebP file to JPG or PNG using a browser-based workflow, and what to expect from output quality and browser support. Useful if you received or downloaded a WebP file and need a format that an older tool or platform accepts.
Covers when converting a JPG to WebP is worth doing, since WebP is usually smaller at similar visual quality, and what compatibility to check first. Read this if you are preparing photos for a website or app and want smaller files without changing your upload workflow.
These guides cover what photo metadata is, where it comes from, and how to check or remove it.
Lists the fields a camera or phone can embed in a photo, such as camera model, timestamp, and GPS coordinates, and explains what each field actually reveals. Read this before removing anything, so you know what you are checking for.
Explains whether platforms such as Facebook and Instagram remove GPS and other metadata from the copy they publish, and what that does and does not guarantee about the original file you uploaded. Read this if you are assuming a platform already handles metadata removal for you.
Checks whether taking a screenshot of a photo reliably drops the original metadata, and notes the new metadata a screenshot itself can add. Read this if "just screenshot it" is your current metadata workaround.
Explains how browser-based metadata removal works, what fields it typically drops, and what it leaves untouched, including verification steps. Read this before sharing a photo publicly or with someone you do not fully trust.
Walks through device-level settings for iPhone, Android, Windows, and Mac to strip GPS data, alongside batch removal in the browser. Read this if you want an operating-system fix in addition to, or instead of, a browser tool.
These guides explain the technical path a file takes through ConvertUnlimited's tools and how to verify the claims made about it.
Describes the mechanical path a selected file takes, from the browser's File API through canvas or a client-side library to the output blob. Read this if you want the plain technical explanation before trusting a tool with a file that matters.
Shows how to independently check, using browser developer tools, whether a given tool's processing step depends on a network request. Read this if you do not want to take the local-processing description on faith.
No. Intent and comparison pages are English-first until data shows a page should be translated and maintained for a target locale.
No. They explain workflows and link to existing tools. Supported file processing still happens locally in the browser for the relevant tools.