MAZANOKE v1.1.5: Self-hosted local image optimizer in your browser — now supports TIFF, ICO, basic auth (featured on Tailscale, LINUX Unplugged, Selfh.st)
-
If you do delve into improving the performance, I suggest using Rust and
no_stdcrates for dealing with images, such as https://docs.rs/zune-jpeg/latest/zune_jpeg/.It would probably take some time to get it working, but it would probably increase performance and support any format you can find a crate for. But it does not seem like it's worth it.
I'll add this to my list of "things I might to when I don't have a side project to waste my time on"
Thanks for your kind words, I tried putting some effort into making the interface a bit more fun and interactive, so thanks for noticing!
In regards to Rust, I've been interested in learning more about it, but I've not had time yet, so it's been in a "soon (tm)" limbo. As I'm comfortable with JavaScript/JS frameworks, sticking with JS was a quick way to get started without much friction.
-
For me this begs the question, why not just a desktop application?
I think @[email protected] put out some great points. On top of this, you can still install MAZANOKE as a PWA, so you "essentially" get a native application experience.
-
Thanks for your kind words, I tried putting some effort into making the interface a bit more fun and interactive, so thanks for noticing!
In regards to Rust, I've been interested in learning more about it, but I've not had time yet, so it's been in a "soon (tm)" limbo. As I'm comfortable with JavaScript/JS frameworks, sticking with JS was a quick way to get started without much friction.
Rust will take time - it has a few concept that I haven't seen in javascript/python/java/C++ family of languages. But it gives "zero-cost abstractions" i.e. a way to write high-level code without any performance penalty. And it has great tooling and WASM support, which is what you'd be after.
But as I said, it is all not worth it now, just for this application.
-
Rust will take time - it has a few concept that I haven't seen in javascript/python/java/C++ family of languages. But it gives "zero-cost abstractions" i.e. a way to write high-level code without any performance penalty. And it has great tooling and WASM support, which is what you'd be after.
But as I said, it is all not worth it now, just for this application.
That's still very interesting to hear, maybe I'll look into it for my next (simpler) project just to try it out.
-
MAZANOKE is a simple image optimizer that runs in your browser, works offline, and keeps your images private without ever leaving your device.
Created for everyday people and designed to be easily shared with family and friends, it serves as an alternative to questionable "free" online tools.
See how you can easily self-host it here:
https://github.com/civilblur/mazanoke---
Highlights from v1.1.5 (view full release note)
The focus of this release has been to improve the core foundation and file format support, but I'm planning to expand with more features further down the road in order to improve the usefulness of MAZANOKE (while still keeping the UX simple).
- Support basic authentication for Docker setups.
TIFFfile format support.- Convert from
TIFF→JPG,PNG,WebP,ICO
- Convert from
ICOfile format support.- Convert from and to an
ICOimage.
- Convert from and to an
---
I also feel incredibly honored that MAZANOKE was recently featured on several of my favorite communities:
It's been incredible to see the growth of the user base, with over 54,000 docker pulls for the previous release alone, and now reaching over 1400 stars! I never anticipated this at all and I'm truly grateful for the support!
I'd like to thank everyone who helped spread the word, whether through starring, word of mouth, community engagement, blog posts, or by packaging it for things like Unraid and NixOS, and everything in between!
Gave it a try by unzipping and running from local index.html, and fed it a 4000*3000 HEIC photo (converting that kind of pics when someone sends them to me would be my main use case) but it has this weird bug that, no matter what format I select, it takes like a couple seconds to convert, it displays that an image of the selected format is ready, but when I click the button it presents a jpeg pic to download. Same happens on mazanoke.com
Using Firefox 139 on win10 if that helps. -
Gave it a try by unzipping and running from local index.html, and fed it a 4000*3000 HEIC photo (converting that kind of pics when someone sends them to me would be my main use case) but it has this weird bug that, no matter what format I select, it takes like a couple seconds to convert, it displays that an image of the selected format is ready, but when I click the button it presents a jpeg pic to download. Same happens on mazanoke.com
Using Firefox 139 on win10 if that helps.If I understand it correctly, the heic image does get read and compressed. However, it's the last part when clicking the download button that it instead displays the image as a jpeg (on a new tab)?
-
If I understand it correctly, the heic image does get read and compressed. However, it's the last part when clicking the download button that it instead displays the image as a jpeg (on a new tab)?
No, not in a new tab. I meant "display" as "it's shown in the processed images list". I upload the heic image, it gets read and compressed, and appears in the processed images list, as it should. But when I click the download button, I get the Firefox dialog to download a jpeg image, and if I proceed, I DO download a jpeg image. Regardless of the conversion format chosen.
(Other little quirk, if "Convert to" is set to JPEG, PNG, webP or ICO, the converted image will be shown in the processed list with the corresponding extension, but if set to Default, it'll show as FILENAME. without extension)
-
No, not in a new tab. I meant "display" as "it's shown in the processed images list". I upload the heic image, it gets read and compressed, and appears in the processed images list, as it should. But when I click the download button, I get the Firefox dialog to download a jpeg image, and if I proceed, I DO download a jpeg image. Regardless of the conversion format chosen.
(Other little quirk, if "Convert to" is set to JPEG, PNG, webP or ICO, the converted image will be shown in the processed list with the corresponding extension, but if set to Default, it'll show as FILENAME. without extension)
Based off the things you mentioned, especially the "little quirk", there something in the pipeline that fails. The file name extension is intended to show regardless of which output format that is selected.
Are you perhaps using a privacy-focused browser like Librewolf (opposed to vanilla Firefox)? Or do you have any extension that might be used for anti-fingerprinting? MAZANOKE need to be able to access the browser's canvas feature in order to convert images, and some browsers are blocking this feature to prevent fingerprinting.
Also, have you tested MAZANOKE on a different browser to see if it works there?
If the issue still persist, would you mind sending me a screenshot of the browser console log, in order for me to see where it fails. This will hopefully provide some hints.
Additionally, while I don't have a Windows environment readily available, I've tested MAZANOKE on Ubuntu and macOS using both firefox and chromium, but I wasn't able to reproduce it. Will test on Windows when I find the chance to.
-
Based off the things you mentioned, especially the "little quirk", there something in the pipeline that fails. The file name extension is intended to show regardless of which output format that is selected.
Are you perhaps using a privacy-focused browser like Librewolf (opposed to vanilla Firefox)? Or do you have any extension that might be used for anti-fingerprinting? MAZANOKE need to be able to access the browser's canvas feature in order to convert images, and some browsers are blocking this feature to prevent fingerprinting.
Also, have you tested MAZANOKE on a different browser to see if it works there?
If the issue still persist, would you mind sending me a screenshot of the browser console log, in order for me to see where it fails. This will hopefully provide some hints.
Additionally, while I don't have a Windows environment readily available, I've tested MAZANOKE on Ubuntu and macOS using both firefox and chromium, but I wasn't able to reproduce it. Will test on Windows when I find the chance to.
Okay, here's what I've found.
First of all, I use vanilla Firefox on windows 10, only extensions installed are AdBlockPlus and Privacy Badger, but even with those turned off and Firefox's own Tracking Protection set to Standard instead of Strict doesn't change the result. However, what I had missed is that ICO is the only conversion that works: it'll take about a minute instead of the couple of seconds of the other cases, generate a file with huge size confronted with the original, but it will let you download an ICO file.
Tried it on Edge, and every conversion works normally. The no-extension quirk for the Default option is still there, though.This is what the Firefox console shows, from page load to the end of the conversion:
Input file:
File` { name: "sample2.heic", lastModified: 1750180660057, webkitRelativePath: "", size: 351970, type: "" } compression.js:43:11
File type is HEIC: image/heic utilities.js:7:13
Input image file size: 0.336 MB compression.js:144:11
Settings:
Object { maxSizeMB: "0.336", initialQuality: 0.8, maxWidthOrHeight: undefined, useWebWorker: true, onProgress: options(p), preserveExif: false, fileType: "image/webp", libURL: "./browser-image-compression.js", alwaysKeepResolution: true, signal: AbortSignal } compression.js:161:11
Preprocessing HEIC image... compression.js:186:11
Optimizing "sample2.heic" (0%) compression.js:119:13
Optimizing "sample2.heic" (5%) compression.js:119:13
Optimizing "sample2.heic" (10%) compression.js:119:13
Optimizing "sample2.heic" (15%) compression.js:119:13
Optimizing "sample2.heic" (20%) compression.js:119:13
Optimizing "sample2.heic" (25%) compression.js:119:13
Optimizing "sample2.heic" (30%) compression.js:119:13
Optimizing "sample2.heic" (99%) compression.js:119:13
Post-processing... compression.js:223:11
New image extension: webp utilities.js:144:11 -
Okay, here's what I've found.
First of all, I use vanilla Firefox on windows 10, only extensions installed are AdBlockPlus and Privacy Badger, but even with those turned off and Firefox's own Tracking Protection set to Standard instead of Strict doesn't change the result. However, what I had missed is that ICO is the only conversion that works: it'll take about a minute instead of the couple of seconds of the other cases, generate a file with huge size confronted with the original, but it will let you download an ICO file.
Tried it on Edge, and every conversion works normally. The no-extension quirk for the Default option is still there, though.This is what the Firefox console shows, from page load to the end of the conversion:
Input file:
File` { name: "sample2.heic", lastModified: 1750180660057, webkitRelativePath: "", size: 351970, type: "" } compression.js:43:11
File type is HEIC: image/heic utilities.js:7:13
Input image file size: 0.336 MB compression.js:144:11
Settings:
Object { maxSizeMB: "0.336", initialQuality: 0.8, maxWidthOrHeight: undefined, useWebWorker: true, onProgress: options(p), preserveExif: false, fileType: "image/webp", libURL: "./browser-image-compression.js", alwaysKeepResolution: true, signal: AbortSignal } compression.js:161:11
Preprocessing HEIC image... compression.js:186:11
Optimizing "sample2.heic" (0%) compression.js:119:13
Optimizing "sample2.heic" (5%) compression.js:119:13
Optimizing "sample2.heic" (10%) compression.js:119:13
Optimizing "sample2.heic" (15%) compression.js:119:13
Optimizing "sample2.heic" (20%) compression.js:119:13
Optimizing "sample2.heic" (25%) compression.js:119:13
Optimizing "sample2.heic" (30%) compression.js:119:13
Optimizing "sample2.heic" (99%) compression.js:119:13
Post-processing... compression.js:223:11
New image extension: webp utilities.js:144:11Thanks a bunch from sharing your result! Based on the fact that ICO works, and I didn't see any real issues in the logs, it could be the "Post-processing..." part where something goes wrong (I didn't add any more detailed logs for that part unfortunately).
Will get back once I've setup a basic Windows development environment and made some tests!
