Image Format Decision Tree

Start with the property you cannot lose. File size is considered only after compatibility, structure, transparency, animation, and quality requirements are safe.

The decision tree

  1. Must layers, paths, or camera-development data remain editable? Keep the working master. Create a derivative only for delivery.
  2. Must motion or multiple pages survive? Use a workflow that explicitly preserves every frame/page; do not use a still-only converter.
  3. Is scalable vector geometry required? Keep trusted SVG or the original vector master.
  4. Is alpha required? Consider PNG, WebP, AVIF, or trusted SVG; exclude JPEG and current ForgeConvert BMP output.
  5. Is it a photograph for broad sharing? Start with JPEG; test WebP/AVIF for known modern destinations.
  6. Is it a screenshot, diagram, or hard-edged graphic? Start with PNG or a suitable lossless mode.
  7. Is it print/scan interchange? Follow the printer or archive specification; TIFF may be appropriate.
  8. Is it an icon package? Follow platform sizes and ICO/SVG/PNG requirements.

Decision table

Goal Shortlist Eliminate when
Universal photo copy JPEG Alpha or master fidelity required
Transparent raster PNG/WebP/AVIF Receiver lacks support
Web photo JPEG/WebP/AVIF Quality or fallback plan fails
Scalable logo Trusted SVG Destination rejects document-like input
High-fidelity interchange TIFF/PNG by workflow Compact browser delivery is primary

Keep-current-format branch

If the existing image already meets the destination’s requirements, do not convert. Avoiding an unnecessary re-encode is a valid decision and can protect metadata, quality, and structure.

Turn the decision into a route

After choosing, use the ForgeConvert Format Selector Guide. Examples include JPG to WebP, PNG to JPG, or HEIC to JPG when each solves the stated requirement.

Scenario walkthroughs

Online product photograph

Keep the camera or editing master, export dimensions for the storefront, then compare JPEG, WebP, and AVIF in supported browsers. Alpha is irrelevant; visual detail and delivery cost dominate.

Logo used in an app and presentation

Keep the vector master. Generate PNG sizes for software that rejects SVG and an ICO package only when the platform requires it.

Scanned contract

Preservation and access are separate. Retain the approved high-fidelity scan and create a smaller delivery copy without replacing the record.

Validation rule

A decision is complete only when the result opens in the destination, preserves every mandatory property, and passes visual inspection. If two candidates pass, choose the simpler supported workflow rather than the newest label.

Decision gates in priority order

  1. Structure: Does the asset require vector paths, animation, multiple pages, layers, or only one raster frame?
  2. Transparency: Is the background opaque, sharply cut out, or softly translucent?
  3. Compatibility: Which browsers, editors, operating systems, printers, or upload services must accept it?
  4. Fidelity: Is loss acceptable, and which details are most sensitive?
  5. Color and metadata: Are profiles, bit depth, orientation, or provenance fields required?
  6. Delivery cost: Which passing candidate has acceptable bytes, decoding behavior, and operational complexity?

Apply the gates in this order. A candidate that fails a mandatory gate leaves the decision tree even if it produces the smallest file.

How to compare finalists

Create finalists from the same trusted master at the same dimensions. Inspect them in the real destination using representative content, then record compatibility, visual quality, required properties, and actual bytes. Include the cost of fallbacks and derivative generation. A format that saves a small amount but adds a fragile delivery branch may not be the better system choice.

Decisions that require more than a format

Format selection cannot decide crop, responsive widths, background removal, document archival policy, accessibility text, or whether a vector should remain editable. Treat these as adjacent requirements. For example, choosing WebP for a hero does not fix an oversized pixel grid, and choosing PNG for a logo does not recreate vector geometry.

Review triggers

  • The destination application or browser baseline changes.
  • A design introduces transparency, animation, or a new background.
  • Performance budgets or print specifications change.
  • The source workflow changes from camera, scanner, or design tool.
  • A platform begins re-encoding uploads.

Related resources