by ready-4-it

Formats & quality

Accepted inputs, target outputs, and honest SVG↔PNG limits.

Pixel Forge is a target-based exporter: one master → many platform-correct sizes and formats. It is not a magic PNG↔SVG converter.

Input formats

Accepted by the GUI file picker:

SVG, PNG, WebP, AVIF, JPG/JPEG, TIFF, GIF, BMP, ICO, ICNS

Quality tier Formats As gallery master?
Preferred SVG; PNG ≥1024 px (alpha when needed) Yes
Acceptable Large WebP/PNG; TIFF; AVIF with alpha Yes, with caveats
Weak JPEG; small PNG/WebP; GIF; screenshots Converts, poor rebuild

Target / output formats

Not PNG-only. Each preset emits what its platform rules allow, for example:

  • Icons: PNG, ICO, ICNS
  • Web / hero: PNG, WebP, AVIF, sometimes SVG copy
  • Store covers: PNG, JPG
  • Favicons: PNG, WebP, SVG, ICO

Common outputs overall: PNG, WebP, AVIF, SVG, ICO, ICNS, JPG.

SVG ↔ PNG (honest)

Direction What Pixel Forge does Quality
SVG → PNG / WebP / ICO / … Rasterizes (CairoSVG / ImageMagick) Usually sharp if the SVG is clean
PNG → SVG No auto-vectorization SVG output only when the source is already SVG (copy / optimize)

If someone expects “PNG in → editable vector SVG out”, that is a different tool class. Pixel Forge scales and packs assets for targets; it does not reverse-engineer logos into vectors.

Traceability

Every run writes metadata.json with source_used per emitted format.