FormatPicFormatPic

How FormatPic Works

FormatPic converts images entirely inside your web browser. Unlike traditional online converters that upload your files to remote servers, FormatPic uses client-side technology to process images on your own device. This page explains the technology behind it, why it matters for your privacy, and how each step of the conversion process works.

The Problem with Traditional Online Converters

When you use a typical online image converter — services like CloudConvert, Convertio, or Zamzar — here is what actually happens behind the scenes:

  1. You select a file on their website.
  2. Your browser uploads the entire file over the internet to the company's servers.
  3. Their server software reads your image, converts it, and stores the result.
  4. The converted file is sent back to your browser for download.
  5. Your original file remains on their server for some retention period (often 1–24 hours).

This workflow creates three issues. First, there is a privacy risk — your personal photos travel across the internet and sit on someone else's computer, even if temporarily. Second, there is a speed penalty — uploading and downloading large files takes time, especially on slower connections. Third, most of these services impose file size limits and conversion quotas because server processing costs money.

How FormatPic's Client-Side Approach Works

FormatPic sidesteps all three problems by performing every step of the conversion locally in your browser. Here is the technical breakdown of what happens when you convert an image:

Step 1: File Reading

When you drag a file into FormatPic or select one from your device, the browser's File API reads the raw image data into local memory. At this point, the file exists only in your browser's RAM — no network request is made, and no data leaves your device. You can verify this by opening your browser's Developer Tools (press F12), switching to the Network tab, and watching for outbound requests. You will see none containing image data.

Step 2: Decoding the Source Format

FormatPic needs to understand the pixels that make up your image before converting to a different format. For standard formats like PNG, JPG, WebP, and GIF, the browser's built-in image decoder handles this natively — every modern browser already knows how to read these formats.

For formats that browsers do not natively support — specifically HEIC (used by iPhones) and AVIF (in browsers without native AVIF support) — FormatPic uses WebAssembly (Wasm) decoders. WebAssembly is compiled code that runs at near-native speed inside the browser's sandbox. FormatPic includes specialized Wasm modules that can decode HEIC and other formats entirely on your device, without any server involvement.

Step 3: Pixel Processing

Once the image is decoded, FormatPic has raw pixel data — an array of red, green, blue, and alpha (transparency) values for every pixel in the image. If you have requested resizing, FormatPic applies high-quality resampling algorithms at this stage. If you are compressing the image, the quality parameter is prepared. All of this processing happens in your browser's JavaScript engine and WebAssembly runtime.

Step 4: Encoding the Target Format

FormatPic renders the processed pixel data onto an HTML5 Canvas element — a drawing surface built into every modern browser. The Canvas API provides native methods to export the image in formats like PNG, JPG, and WebP. For each format, you can control quality settings (for lossy formats) and dimensions.

For formats that require specialized encoding (like ICO for favicons or TIFF for print workflows), FormatPic uses additional JavaScript libraries that run entirely in the browser. No server round-trip is needed for any supported format.

Step 5: Download

The converted image is created as a Blob (binary large object) in your browser's memory. When you click Download, the browser generates a local URL pointing to this in-memory file and triggers a standard file download. The file goes directly from your browser's memory to your hard drive. At no point does the image pass through FormatPic's servers or any external service.

Supported Formats and Their Differences

FormatPic supports 10 image formats, each designed for different purposes. Understanding the differences helps you choose the right output format:

JPG (JPEG) — The Universal Photo Format

JPG uses lossy compression tuned for photographs. It analyzes the image and discards visual information that human eyes are unlikely to notice — a process based on psychovisual modeling. At quality settings of 80–90%, JPG produces remarkably small files with negligible visible quality loss. The tradeoff: JPG does not support transparency, and each re-save at lossy quality degrades the image slightly. JPG has been the web's default photo format since the 1990s, and it works on every device and application ever made.

PNG — Lossless with Transparency

PNG uses lossless DEFLATE compression — no pixel data is discarded, ever. This makes PNG ideal for screenshots, logos, text-heavy graphics, and any image where you need pixel-perfect accuracy. PNG supports full alpha transparency, meaning each pixel can be partially transparent. The downside is file size: a PNG photo can be 5–10 times larger than the same image saved as JPG.

WebP — The Modern Standard

Developed by Google, WebP supports both lossy and lossless compression with transparency and animation — combining the best features of JPG, PNG, and GIF in a single format. Lossy WebP images are typically 25–34% smaller than JPG at the same visual quality. As of 2026, WebP enjoys approximately 97% global browser support, making it the recommended format for most web images.

HEIC — Apple's Efficient Format

HEIC uses the HEVC (H.265) video codec to compress still images, achieving roughly 50% smaller files than JPG at equivalent quality. Every iPhone since 2017 shoots HEIC by default. The limitation is compatibility — Windows requires a separate extension to view HEIC files, web browsers cannot display them natively, and most image editing software does not support HEIC. Converting HEIC to JPG or WebP is one of the most common operations on FormatPic.

AVIF — Next-Generation Compression

AVIF uses the AV1 video codec (royalty-free, backed by the Alliance for Open Media) for still images. It outperforms both WebP and JPG in compression efficiency, often producing files 30–50% smaller than JPEG at the same visual quality. AVIF supports HDR, wide color gamut, and transparency. Browser support is expanding rapidly but is not yet universal, making AVIF best suited for progressive enhancement alongside JPG or WebP fallbacks.

GIF, BMP, TIFF, SVG, ICO

FormatPic also supports GIF (limited-color animation format), BMP (uncompressed Windows bitmap), TIFF (high-quality archival and print format), SVG (scalable vector graphics for logos and icons), and ICO (multi-resolution favicon format). Each serves a specific niche, and FormatPic handles conversions between all of them.

Privacy Benefits of Client-Side Processing

The architectural decision to process images client-side is not just a performance optimization — it is a fundamental privacy guarantee. Here is why it matters:

  • Zero data transmission — Your images never travel over the internet. There is no network request containing your files, so there is nothing to intercept, log, or leak.
  • No server storage — FormatPic has no servers that receive or store user images. There is no database to breach, no backup to expose, and no log file containing your file names or metadata.
  • No trust required — You do not need to rely on a company's promise to delete your files. The architecture makes it physically impossible for your images to reach FormatPic's infrastructure.
  • Verifiable — Unlike privacy policies that you have to take on faith, client-side processing can be independently verified. Open your browser's Developer Tools, monitor network traffic, and confirm that no image data is transmitted.
  • Works offline — After loading the page, FormatPic can convert images without any internet connection. Disconnect your Wi-Fi and try it — if the conversion still works, your files clearly are not going anywhere.

This matters especially for personal photos (which often contain GPS metadata, faces, and private moments), professional work under NDA, legal or medical documents, and any image you would not want stored on a stranger's server.

Batch Conversion and Performance

FormatPic supports converting multiple images simultaneously. When you select several files, each is processed independently using the same client-side pipeline described above. Modern browsers handle this efficiently by leveraging your device's multi-core processor. A batch of 50 images that might take several minutes on a server-based tool (due to upload and download latency) typically completes in seconds on FormatPic.

There is no artificial limit on the number of files you can convert. The practical limit is your device's available memory — most modern computers and phones can handle dozens of images without issue. For very large batches (hundreds of high-resolution images), you may want to process them in groups of 20–30 to keep memory usage reasonable.

Browser Compatibility

FormatPic works in all modern browsers: Chrome, Firefox, Safari, and Edge on desktop and mobile. It relies on standard web APIs (Canvas, File API, Blob) that have been available in all major browsers for years. For HEIC decoding, WebAssembly support is required — this is available in all browsers released since 2017.

For the best experience, we recommend using the latest version of your browser. Newer browsers include performance improvements and expanded format support (for example, Safari added native AVIF support in version 16.4, and Firefox added it in version 113).

Try It Yourself

Ready to convert an image? Head to the converter and try it out. You can also explore specific tools: