Mirror takes a supplied design or reference image, a web implementation and a chosen viewport, then reports how closely the rendered result matches.
Mirror has not launched. Everything described here is the planned Local V1 scope, and anything explicitly marked upcoming is later work rather than something you can use today.
- Status
- In development
- Rendering engine
- Chromium, as the authoritative first engine
- Account
- Local V1 planned to work without a Paddy Systems Account
- Data
- Local references, captures and reports stay local by default
The intended workflow
- 01
Reference image
The supplied design or reference the implementation should match.
- 02
Target implementation
The web implementation being compared.
- 03
Chosen viewport
The comparison is made at a viewport you choose.
- 04
Deterministic capture
Chromium is the authoritative first rendering engine.
- 05
Visual comparison
Reference and capture measured against each other.
- 06
Report
The result, with the evidence that produced it.
What the planned Local report shows
- Reference
- Captured implementation
- Primary result
- Overlay / opacity comparison
- Difference view
- Threshold / score
- Mismatch regions
- Viewport / render metadata
What Mirror will and won't claim
Captures, differences, thresholds and mismatch regions are measurements taken from a deterministic render. They stay clearly separated from anything inferred.
- Mirror is not a generic DOM or CSS debugger.
- Mirror does not claim it can automatically fix your source code.
- Inferred guidance is never presented as a measured result.
Later, and clearly marked as later.
- Mirror Cloud
- Account-backed projects, history and collaboration
- GitHub / pull request workflows
- CI integrations
- Figma integration
- Paid Cloud capabilities
There is no waitlist and no published Mirror pricing. When Local V1 is ready to use, the product page will say so plainly.