How PixelShift processes files

What runs in the browser, what is downloaded, and what analytics collects.

This page describes the application code. It is not legal advice and it is not a certification.

Image conversion, resize, crop, compress, image-to-PDF, PDF compress, PDF-to-image, HEIC decode, RAW preview extraction, SVG rasterizing, and AI upscale run in the browser. Your files aren't uploaded to a server.

What stays on the device

  • JPG, PNG, and WebP export use the browser canvas encoder (canvas.toBlob).
  • AVIF export uses @jsquash/avif, loaded with the app. PixelShift passes only a quality number. The encoder's no-loss option is left off.
  • HEIC and HEIF are decoded with heic2any, loaded with the app, to a JPEG at 80% quality before the canvas export.
  • Sony ARW and Nikon NEF use a Web Worker that reads an embedded JPEG preview. They are not a RAW demosaic.
  • SVG is drawn by the browser and rasterized. It is not kept as vectors.
  • Image to PDF uses jsPDF in the browser and embeds a JPEG at 85% quality.
  • PDF compress uses pdf-lib in the browser and recompresses embedded images as JPEG.
  • PDF to image uses pdf.js in the browser, paints each page on a canvas, and encodes PNG, JPG, or WebP. Text in those images is not selectable.
  • AI upscale runs ESRGAN Thick 2× with TensorFlow.js WebGL inside a Web Worker.

What the browser downloads

These downloads are app code or model weights. They are not your image bytes leaving the device.

  • The site's JavaScript, including the HEIC, AVIF, and PDF libraries, is loaded from this site when needed. PDF to image also loads font, CMap, and wasm files from /pdfjs/ on this site.
  • The HEIC library embeds its WebAssembly decoder in that script. The package source has no remote codec URL.
  • The AVIF encoder loads its WebAssembly file from the same origin as the app script.
  • The first AI upscale fetches ESRGAN weights from /models/esrgan-thick/x2/ on this site. Later visits can reuse the browser cache.

Analytics, only after you accept

Google Analytics 4 is not loaded until you accept the cookie banner. The choice is stored in localStorage as pixelshift_analytics_consent. Rejecting it leaves conversion unchanged.

If you accept, events can include:

  • page_view: page title, path, and a fixed acquisition label such as google, direct, or referral_other.
  • tool_open, file_selected, conversion_completed, and download_completed.
  • Counts and labels: tool name, file count, input format, output format, conversion mode, and download type.

The analytics code strips blob URLs, file paths, and filenames before sending. It does not send image bytes, PDF bytes, or pixel data. The script itself is loaded from https://www.googletagmanager.com/gtag/js only after consent.

For the processing steps and how to watch the network panel, see the security architecture page.

PixelShift.cc

Secure Client-Side Converter...