I built BulkPixel because image conversion is one of those small tasks that somehow keeps interrupting real work.
Resize a batch of screenshots. Convert PNGs to WebP. Export the same assets in different sizes. Rename files. Remove metadata. Repeat the exact same setup a few days later.
None of these tasks is particularly difficult on its own, but together they quickly become repetitive. When you work on websites, documentation, articles, apps, or other digital projects, you often end up doing the same image-processing steps again and again. I wanted a tool that would make these workflows faster without adding another complicated system to manage.
There are plenty of tools that can do parts of this, but I wanted something focused, local-first, and easy to automate.
BulkPixel is a free and open-source macOS app for batch image conversion, resizing, and automation. You can drop in multiple images, choose an output format, resize by width or height, adjust quality, change filenames, remove EXIF metadata, and export the whole batch at once.
For workflows you repeat regularly, you can save everything as a preset: format, dimensions, quality, naming rules, and output directory. Instead of configuring the same settings every time, you can define the workflow once and reuse it whenever you need it.
One of my favorite features is Magic Directories. You can watch a folder and connect one or more presets to it. Whenever matching images are added, BulkPixel processes them automatically while the app is running.
For example, you could create a folder for blog images and automatically convert every new image to WebP, resize it to a specific width, remove metadata, and save the result in the correct output directory. This turns BulkPixel from a simple converter into a lightweight image-processing workflow.
There is also a CLI, so the same presets can be used from the terminal or integrated into scripts:
bulkpixel convert --preset "Blog Header" --input ./image-1.png ./image-2.png
This was important to me because image processing is often part of a larger development or publishing workflow. A graphical interface is convenient for manual tasks, while a CLI makes it possible to integrate the same configuration into scripts and automation.
BulkPixel also keeps local statistics about your workflow, including the number of conversions, formats used, input and output storage, saved space, and processing time. This gives you a simple overview of how much image processing you are actually doing and how much storage optimization you are getting from different formats.
Everything runs locally on your Mac. There is no account, no cloud upload, and no subscription. Your images stay on your machine throughout the entire process.
Supported input formats include JPG, JPEG, PNG, WebP, and AVIF, with exports to JPEG, PNG, WebP, and AVIF.
The project is completely open source under the MIT license and available on GitHub. You can also install the app and CLI through Homebrew.
My goal with BulkPixel is simple: make repetitive image work boring again.
Instead of spending time repeatedly configuring exports, renaming files, resizing assets, or manually converting images, I want BulkPixel to handle those repetitive steps so you can focus on the actual project.
I’d love to hear how you handle bulk image workflows today, what parts of the process still feel unnecessarily repetitive, and what features, formats, or automation options you’d like to see in BulkPixel next.
Explore more design tools tools on EarlyHunt.


Comments
Sign in to post a comment or reply
No comments yet
Be the first to comment!