About FreeTinyPNG
Free, private, browser-based image tools for everyone.
Last updated: April 18, 2026
Our mission
FreeTinyPNG was built around a simple belief: basic image tools should be free, fast, and private. Every web designer, blogger, marketer, and student needs to compress and convert images, and yet the most popular tools online either charge a subscription, impose strict file-size limits, or upload your private images to a remote server.
We do none of those things. Every tool on this site runs entirely inside your browser. Your files never leave your device, there is no signup, and there is no usage limit beyond what your own hardware can handle.
What we offer
We focus on a small set of tools, done well:
- Image compression for PNG and JPG, including bulk processing.
- Format conversion between PNG, JPG, and the modern WebP format.
- In-depth guides and tutorials explaining how image formats work and how to choose the right one for your project.
We deliberately keep the toolset small. We would rather have three excellent tools than thirty mediocre ones. If a tool is on this site, you can trust that it has been thought through carefully.
How we work
Our tools are built on three principles:
Privacy first. All processing is performed in the browser using the native Canvas and WebAssembly APIs. We have no servers that handle your image data. We couldn’t see your files even if we wanted to. You can confirm this yourself by opening your browser’s Developer Tools and watching the Network tab as you process a file.
No artificial limits. We don’t gate features behind paywalls or restrict the number of files you can process per day. The web should be a place where useful tools are available to everyone.
Honest engineering. Compression is governed by the laws of information theory. We don’t promise impossible savings, and we don’t recompress files in ways that would degrade them invisibly. When a file can’t get smaller without losing quality, we tell you.
How we’re funded
FreeTinyPNG is supported by display advertising shown alongside the tools and articles. We do not sell user data, place tracking pixels for third-party advertisers, or operate any subscription tier. Ads pay for the domain, hosting, and the time it takes to write and maintain the site.
If our advertising ever begins to interfere with the tools (slow page loads, intrusive overlays, deceptive placements), we consider that a bug and want to hear about it. Email us at [email protected].
Meet the editorial team
FreeTinyPNG is written and edited by a small team of engineers, designers, and writers who have each spent years dealing with image problems in their day jobs. Articles are signed by the person who wrote them, not by a generic “team” byline.
Liam Harris — Editor-in-chief
Based in London, United Kingdom. Liam spent ten years as a front-end engineer on high-traffic e-commerce teams before moving into editorial work full-time. He’s shipped image pipelines on Rails, Next.js, and several Jamstack stacks, and has strong opinions about when to choose each. He joined FreeTinyPNG to make the practical knowledge he’d built up available to teams who don’t have a dedicated performance engineer. When he isn’t writing, he’s usually rebuilding a vintage mechanical keyboard.
Writes: technical deep-dives on compression, Core Web Vitals, performance engineering.
Mei Zhang — Senior Editor, formats & workflows
Based in Singapore. Mei started her career as a UX designer at a regional digital publisher, where she eventually owned the image-handling guidelines for the entire newsroom. She’s seen first-hand how choosing the right format and sizes ripples through everything from CDN bills to reader retention, and that’s the lens she brings to her writing. She has a soft spot for WebP and a near-religious belief in resizing images before you compress them.
Writes: format guides, CMS-side optimization, practical how-to articles.
Samuel Ortega — Staff Writer, photography & e-commerce
Based in Mexico City, Mexico. Samuel spent several years as a technical writer at a stock-photo platform, where he learned the practical trade-offs between file size, resolution, and visual quality by answering thousands of support tickets. He shoots product and street photography on the weekends and still keeps a color-calibrated external monitor on his desk. His writing focuses on the small, recurring problems content creators and online sellers run into every week.
Writes: product photography, social-media formats, everyday publishing pain points.
Our editorial standards
Every guide and article on this site is written and edited by one of the people above. We:
- Verify every technical claim before publication.
- Cite primary sources (W3C specifications, browser documentation, academic papers) where appropriate.
- Update articles when the underlying technology changes. When browser support for a format expands, for example, or when a new compression algorithm becomes the de facto standard.
- Disclose limitations and trade-offs honestly. There is no perfect format and no magic compression algorithm. We tell you what each tool actually does.
We do not publish AI-generated content without substantial human review and editing. Articles bearing an author byline have been written or substantively edited by the named author.
Contact us
We welcome questions, feedback, bug reports, and suggestions. The best way to reach us is by email at [email protected], or via the form on our contact page.
If you found an issue with a tool, please include:
- Which tool you were using.
- Your browser and operating system.
- The approximate size and format of the file you were processing.
- A description of what went wrong and what you expected to happen.
We aim to respond to every email within a few business days.