# Test record: PNG -> WebP

- Date: `2026-07-30`
- Build: `LocalFlux 1.0.7.0 (product build 1.0.7.0+6c828b7d7c8e2e070a2db0206a106adb877affcf)`
- Environment: `Daily-use Windows x64 host, Windows build 10.0.26200.0`
- Environment label: `DailyUseX64` (not clean-VM evidence)
- Route: `PNG -> WebP`
- Runtime: `bundled ImageMagick`
- Source: `samples/website-hero.png`
- Output: `samples/website-hero_converted.webp`
- Source SHA-256: `5517E7DE92F9D1EAF74594F7D387C3B14D4A7FDBF096EE491FCB3182CB573BF2`
- Output SHA-256: `C783FA118C34F2C83D54DC47E5524A7EE20FB66A5F40471CADF227085CDDDB3E`

## Observations

- The 96 x 64 opaque PNG was converted to a 96 x 64 WebP.
- Input size was 3,465 bytes; output size was 726 bytes (about 79% smaller for this fixture).
- The original remained unchanged and the output used the `_converted` suffix.

## Limitations

- The fixture is opaque and does not prove transparent-edge behavior.
- The fixture has no representative EXIF, XMP, ICC, or text metadata.
- One synthetic file does not predict savings for production images.

## Repository evidence consulted

- `src/LocalFlux.Core/Data/routes.json` for the explicit route.
- `tests/Samples/route-matrix.md` and route acceptance tests for runtime coverage.
- `src/LocalFlux.Core/Services/FfmpegArguments.cs`, `ImageMagickArguments.cs`, or the LibreOffice executor as applicable.
- `docs/store/landing-page-copy.md` for local-processing, offline, safe-output, and claim guardrails.

## Review result

`PASS` for this fixture and captured build, subject to the limitations above.