This solves a very real pain. I’ve wasted so much time re-exporting the same image 4–5 times just to hit size limits, especially for blog posts and tools pages.
The “resize first, then adjust quality only if needed” approach makes a lot of sense — that’s exactly the workflow most of us do manually.
One small suggestion: if it can show a live preview + final file size before export, that would make it even more practical for daily use.
That’s a great suggestion. When you say live preview + final file size, do you mean seeing the resized image in-app before saving, or primarily having an accurate file size estimate before export? Trying to keep the tool lightweight, so I’d love to understand what would make it most useful in your workflow. And would it be acceptable if it was a checkbox like 'show previews for approval' so that sort of feature came up, otherwise just process through them as normal?
This is a great utility. I’ve run into that exact Lightroom/Photoshop frustration where you're just guessing quality sliders to hit a kb limit. I actually just launched a tool called MyResumeFit to solve a similar 'guessing game' for job seekers (scoring resumes against ATS).
Quick question Since it runs entirely locally, are you using WebAssembly for the image processing ?
I stuck with the standard imaging processing, Pillow. A very strong library, offers opportunity to add features down the road if there is interest (watermarks, etc)
This is very useful! I just spent the last few days struggling with image aspect ratios and thumbnails for my mobile app.(Plant-a-Tree) Preparing images for the web/mobile while keeping the UI clean is always a challenge. Did you use any specific library for the image processing or is it all custom? Great work:)
It’s built on standard image processing libraries rather than reinventing everything from scratch (in this case Pillow). The resizing and compression logic is straightforward, but the main focus was making the output predictable — max dimension first, then only reducing JPEG quality if needed to hit the file size target.
I wanted to avoid the typical “export, check size, tweak quality, repeat” loop.
Right now it is general on purpose. max dimension and max file size without repeated export cycles. The initial pain was hitting CDN limits and OG image constraints without guessing quality settings. I wanted predictable output in one pass.
If enough people care about specific presets (OG images, Twitter cards, etc.), I’d probably add named profiles.
If anyone here works with photography workflows, I’d genuinely be interested in how you handle export constraints today. Lightroom presets? Custom scripts? Just trial and error?
About
Built to avoid guessing export settings. Enforces max pixel size and file size in one predictable pass. Local tool, no cloud. I was tired of exporting the same file for different settings from Lightroom.
11 Comments
This solves a very real pain. I’ve wasted so much time re-exporting the same image 4–5 times just to hit size limits, especially for blog posts and tools pages.
The “resize first, then adjust quality only if needed” approach makes a lot of sense — that’s exactly the workflow most of us do manually.
One small suggestion: if it can show a live preview + final file size before export, that would make it even more practical for daily use.
That’s a great suggestion. When you say live preview + final file size, do you mean seeing the resized image in-app before saving, or primarily having an accurate file size estimate before export? Trying to keep the tool lightweight, so I’d love to understand what would make it most useful in your workflow. And would it be acceptable if it was a checkbox like 'show previews for approval' so that sort of feature came up, otherwise just process through them as normal?
This is a great utility. I’ve run into that exact Lightroom/Photoshop frustration where you're just guessing quality sliders to hit a kb limit. I actually just launched a tool called MyResumeFit to solve a similar 'guessing game' for job seekers (scoring resumes against ATS).
Quick question Since it runs entirely locally, are you using WebAssembly for the image processing ?
I stuck with the standard imaging processing, Pillow. A very strong library, offers opportunity to add features down the road if there is interest (watermarks, etc)
This is very useful! I just spent the last few days struggling with image aspect ratios and thumbnails for my mobile app.(Plant-a-Tree) Preparing images for the web/mobile while keeping the UI clean is always a challenge. Did you use any specific library for the image processing or is it all custom? Great work:)
Thanks — glad it helped.
It’s built on standard image processing libraries rather than reinventing everything from scratch (in this case Pillow). The resizing and compression logic is straightforward, but the main focus was making the output predictable — max dimension first, then only reducing JPEG quality if needed to hit the file size target.
I wanted to avoid the typical “export, check size, tweak quality, repeat” loop.
Nice, hitting both max dimension and file size without repeated exports is a surprisingly common pain. Local + predictable output is a strong combo.
Are you’re targeting specific web constraints (e.g., OG images, app assets, CDN limits) or keeping it general?
Right now it is general on purpose. max dimension and max file size without repeated export cycles. The initial pain was hitting CDN limits and OG image constraints without guessing quality settings. I wanted predictable output in one pass.
If enough people care about specific presets (OG images, Twitter cards, etc.), I’d probably add named profiles.
Hey Paul, this actually solves a real pain, I've seen photographers deal with this exact Lightroom export loop more times than I can count.
Are you planning to add a landing page for it, or keeping it purely GitHub for now?
For now it's GitHub only, keeping it small and focused.
If it gets consistent usage I'll probably give it a simple landing page to show use cases and such.
If anyone here works with photography workflows, I’d genuinely be interested in how you handle export constraints today. Lightroom presets? Custom scripts? Just trial and error?