One edit log, one core, the same image everywhere
Sealpixel renders in the browser and on the server from the same WebAssembly core. These pages show what that buys: a large photo edited without ever loading it, a byte-identical render on both sides, and the editor inside four frameworks.
- Server renderA photo too large for the browser: the editor works on a proxy, the server renders the original, and the numbers are shown at every step.
- ParityThe same edit log rendered locally and on the server, with both hashes side by side.
- React, Vue, Svelte, VanillaThe same editor in four framework wrappers, driven by one shared edit log.
- ResumeAn edit log saved and reopened: the image comes back at the state it was left in.
- CustomizePresets, design tokens, ::part hooks and six languages, restyling the editor live.