Dezoomify finds the full image behind a zoomable viewer and assembles its tiles into a picture you can save.
- Website: paste the viewing page address, then save a PNG. No installation; browser image-size limits apply. Guide.
- Browser extension for Chrome and Firefox: finds hidden image addresses and uses your source-page login. Guide.
- Desktop app: Windows, macOS, and Linux; larger images, local files, more output formats, and cached tiles for interrupted saves. Installation and use.
- Command-line tool: native saving for scripts, image/level selection, and lists of addresses.
The apps recognize IIIF, Deep Zoom, Zoomify, Google Arts & Culture, krpano, and other formats. The legacy website remains available.
Use the extension for signed-in pages and desktop for images beyond browser limits. For missing images, access refusals, and interrupted saves, see troubleshooting or find the image address manually.
Before reporting a problem, search existing issues for the site. Include the viewing page, the address you gave Dezoomify, the app, and its error or diagnostic report. Review reports for sensitive addresses before sharing.
Install Rust and the Node.js version in .node-version.
Native x86-64 builds need NASM 2.15 or newer for AVIF SIMD
(apt install nasm, brew install nasm, or choco install nasm).
cargo xtask setup
cargo xtask check
cargo xtask test
cargo xtask dev webSetup installs frozen JavaScript dependencies and checks WASM tools; install
Rust toolchains and browser binaries separately. Native builds bundle the
offline viewer using Node, so run setup before building them.
Use cargo xtask --help for build, development, and test targets.
Desktop prerequisites are platform-specific.
To build the CLI, run cargo xtask build cli, then:
target/debug/dezoomify-cli "https://museum.example/collection/painting" painting.pngContribution rules are scoped in AGENTS.md. Start format support in
crates/dezoomify/ with a
shared product fixture. Release recovery
and licensing provenance have separate records.
All four apps use the same Rust downloader. Platform adapters connect it to browser or operating-system capabilities, while each app handles its own user interaction. The graphical apps also share their presentation layer.
| Piece | Role |
|---|---|
| Website | Browser app and public-resource proxy; functions provide deployed server entry points. |
| CLI, desktop, extension | Product entry points for terminal use, native saving, and browser-session access. |
| Shared algorithm | Image discovery, resolution selection, and tile-download policy used by every product. |
| Native runtime, browser runtime | Platform capabilities supplied to the shared algorithm. |
| WASM bridge, bindings | Connection between the Rust algorithm and JavaScript products. |
| Shared UI | Common screens, presentation, and translations for the graphical apps. |
| Page agent | Viewer information and tile access available inside a source page. |
| Tests, product fixtures, historical data | Shared regression coverage and reproducible image sources, alongside component-local tests. |
| Task runner, scripts, workflows | Development, validation, packaging, and publication. |
| User guides, release runbook | Help for using the apps and operating releases. |
| Legacy website | Preserved older app, served separately from the current website. |