TPToolpazar

Global Araç

Universal Image Converter

Conversion happens entirely in your browser via Canvas API — your images never leave your device. JPG output requires opaque background (we use white). PNG preserves alpha; WebP also preserves alpha at any quality level. GIF / BMP / TIFF input is decoded if your browser supports it (Chrome and Safari do; Firefox covers GIF + BMP).

The image format ecosystem is more complex than most users realize: JPG (1992) for photos, PNG (1996) for screenshots and graphics with transparency, GIF (1987) for short animations and palette art, BMP (1990) as Windows’ legacy uncompressed format, WebP (2010) as Google’s modern everything-format, AVIF (2019) as the newest most-efficient codec, HEIC (2017) as Apple’s default phone format, and TIFF for archival/print workflows. Each has different strengths in compression efficiency, transparency support, color depth, and ecosystem compatibility — and each browser, operating system, social platform, and email client supports a slightly different subset. A universal converter is the practical solution: drop in whatever you have, get back what your destination needs.

This converter accepts JPG, PNG, WebP, GIF, and BMP as input (using the browser’s native decoder for each), and outputs JPG, PNG, or WebP via Canvas.toBlob(). Quality slider (0-100, default 80) applies to lossy formats (JPG, WebP). PNG output is lossless and parameter-free. Batch mode handles multiple files in sequence with the same target settings — useful for asset-pack standardization (every product photo to 800px-wide JPG @ 85%, every diagram to PNG). All processing runs locally; nothing uploads.

Choosing the right output: WebP is the default winner for the modern web — 25-35% smaller than JPG at equivalent quality, with full alpha channel like PNG. Compatibility is universal in modern browsers (Chrome 17+, Firefox 65+, Safari 14+, Edge all). Pick JPG for maximum compatibility (still works everywhere, smaller than PNG for photos) or when the destination explicitly requires JPG. Pick PNG for transparency-required graphics (logos with cutouts, icons) or when you need lossless. AVIF would be even better than WebP but requires a heavier encoder; most browser-based tools omit it. For photos this tool will not match what modern AVIF encoders ship.

Nasıl Kullanılır

  1. Drop one or more image files (JPG, PNG, WebP, GIF, BMP all accepted).
  2. Pick target format: JPG (universal compatibility), PNG (lossless + transparency), or WebP (modern web default).
  3. For lossy formats (JPG/WebP), set quality 50-100 (80 is the visually-lossless sweet spot).
  4. Click Convert; outputs appear with download links.
  5. For batch jobs, all files use the same target settings — process in groups if you need different outputs.

Ne Zaman Kullanılır

  • Standardizing image asset packs to a single format and quality.
  • Converting iPhone HEIC photos to web-friendly JPG/WebP/PNG (use the dedicated HEIC tools for HEIC input — this tool doesn't decode HEIC).
  • Quick one-off conversions for email attachments, web uploads, or design work.
  • Comparing file size at different quality settings before bulk processing.
  • Stripping JPG metadata accidentally — re-encoding via Canvas drops EXIF.

Ne Zaman Kullanılmaz

  • HEIC input — the browser doesn’t decode HEIC natively; use the HEIC-to-X tools that ship heic2any.
  • AVIF output — most browser Canvas implementations don’t expose AVIF encoding; use a desktop tool.
  • Animated GIF preservation — converting animated GIF outputs only the first frame (still image).
  • EXIF-preservation workflows — Canvas-based conversion strips metadata; use desktop tools (ExifTool, jpegtran) if you need EXIF passthrough.
  • Massive batches (1000+ files) — browser-based is fine up to ~50 files; for hundreds use ImageMagick CLI.

Yaygın Kullanım Senaryoları

  • Verifying a number or output before passing it on
  • Quick conversion during a typical workday
  • Pre-decision sanity-check on inputs and outputs
  • Educational use — demonstrating the underlying concept

Sık Sorulan Sorular

Why is JPG output white where there was transparency?

JPG has no alpha channel — it can’t represent transparent pixels. The Canvas tool fills the background white before drawing the image, so anywhere transparent in the source becomes white in the JPG output. To preserve transparency, output to PNG or WebP instead. Both support full alpha channel.

What quality should I use for JPG/WebP?

80 is the visually-lossless sweet spot for most content — output is indistinguishable from original at typical viewing sizes. 90+ is overkill for web use. Below 70 starts showing visible compression artifacts. For thumbnails or low-stakes use, 60-70 is fine. For photo printing or detailed graphics, 90+. WebP at 80 typically beats JPG at 85 for both quality and size.

Will I lose quality converting to a lossy format?

Yes, every lossy compression cycle introduces loss. Going PNG → JPG → PNG won’t magically recover the lost JPG data. Going JPG → JPG (re-encoding at the same or higher quality) introduces fresh artifacts in addition to the existing ones. Best practice: keep an original lossless source (PNG or RAW) and re-encode to lossy formats only at distribution time, not iteratively.

What about WebP support — is it safe for emails?

Modern email clients (Gmail web, Outlook web, iOS Mail) display WebP fine. Older desktop clients (Outlook 2016, some corporate email gateways) may show broken-image icons. For email attachments specifically, JPG is still the safest. For inline images on a website you control, WebP is fine. For emails to unknown audiences, default to JPG.

Why is the converted file size sometimes bigger than the original?

Re-encoding can produce a larger output when (1) you increase quality from the source, (2) you convert lossy to lossless (JPG → PNG), or (3) the source was already heavily compressed and your re-encoder is conservative. Check size before downloading; if larger and unexpected, lower the quality slider or pick a different output format.

Does it preserve EXIF metadata?

No. Browser Canvas operations strip EXIF (camera info, GPS, timestamp, lens). For metadata-preserving conversion, use desktop tools: ExifTool with -overwrite_original_in_place, ImageMagick’s magick command with -define preserveBkgd, or photo-management apps like XnConvert. Stripping is sometimes desired (for privacy when sharing) so this isn’t always a downside.