No hidden upload path
Inspect the file flow and confirm that compression does not depend on a Zestkit image-storage service.
Zestkit says your images stay in the browser. You do not have to take that sentence on trust: trace the processing path, inspect every network boundary, or run the same code yourself.
VERIFY THE CLAIM
The public repository is useful because it connects a privacy statement to concrete implementation. Start with the file boundary, continue through the worker, and finish at the measured Blob that becomes your download.
Compression worker
web/src/workers/compress-image.worker.tsFollow the quality search, dimension reduction, and final byte-limit check away from the main UI thread.
Validation and job control
web/src/lib/image-compression.tsInspect file signatures, static-image checks, worker messages, cancellation, and result verification.
Format conversion worker
web/src/workers/convert-image.worker.tsSee how supported images are decoded and exported locally as JPG, PNG, or WebP.
WHY OPEN SOURCE MATTERS HERE
Inspect the file flow and confirm that compression does not depend on a Zestkit image-storage service.
Read the final Blob-size check that runs before a successful compressed result is exposed for download.
Run the same interface and workers locally or deploy your own copy without creating a Zestkit account.
Use, study, modify, and distribute the project under a short, permissive open-source license.
The repository contains one Next.js application in the web directory. No database, account system, or image-processing API is required for the current tools.
git clone https://github.com/Barry5753/Zestkit.git
cd Zestkit/web
pnpm install && pnpm devUSE OR CONTRIBUTE
Try the live tools first, read the code path that matters to you, or open a focused issue when you find a reproducible problem.
Yes. The browser interface, validation code, compression worker, conversion worker, and final result checks are all available in the public repository.
Yes. Clone the repository, install the web app dependencies with pnpm, and start the local Next.js development server. The exact commands are shown on this page and in the README.
Zestkit is released under the MIT License. You may use, copy, modify, and distribute it under the terms in the repository's LICENSE file.