Convert, resize, optimise. All in one window.
Drag in an SVG and get a PNG. Drag in a whole folder of photos and get JPEGs at the size you need. The everyday image jobs that ought to take ten seconds, done in ten seconds, without opening anything bigger.
macOS 15 or later. Apple silicon Mac. Version 1.1.0, out 11 October 2026. What’s new.
Six pictures on their way to less than half the size. The app worked those numbers out for real before anything was saved.
ImageOptim has been in my Dock for years and I still rate it. What I kept wanting was that, with resizing and file type conversion in the same window, so I stopped searching “svg to png” and handing my work to whichever website came up first. This is the result.
Convert
An SVG to a PNG. A HEIC to a JPEG. Anything to WebP for a website. If your Mac can open it, this can turn it into something else.
Resize
Half size, twice the size, or a width you type in. A whole app icon, every size inside it, from one picture. It never blows a photo up bigger than it really is.
Optimise
Make the file smaller without changing what it is or how it looks. Leave everything alone and this is what it does by default.
Three steps, and the third one is a button
The window opens with two menus and an Export button. The first menu is what you came for; most people never touch anything else.
- Drag them inOne picture, a handful, or a whole folder. You can also right-click files in Finder and open them with it.
- Choose what you wantTwo menus at the top: what kind of file, and what size. That is all most people ever touch.
- Press ExportSave the new files next to the old ones, into a folder you pick, or over the originals. Replacing puts the old ones in the Trash, so you can always get them back.
Where you start. Drag a folder onto it and every picture inside lands in the window.
One window, nine jobs
It does not try to do everything, and it is not meant to. It does the ninety per cent most of us need without opening Photoshop or Figma, and it does those properly. None of them ask you to know anything about image formats.
Turns one kind into another
An SVG into a PNG. An iPhone photo into a JPEG. A screenshot into a WebP for your website. Pick what you want out and that is what you get.
Logos and PDFs, at any size
Drop in an SVG or a PDF, say how big, and it comes out sharp rather than blurry. This is the one that is genuinely awkward to do any other way.
A whole folder in one go
Drag in fifty files and they all get the same treatment. Most converter sites do one at a time and put a limit on it.
Resizes without the maths
Half size, quarter size, or type in the width you need and it works the height out for you.
Makes files smaller on its own
If you do not ask for anything else, it just shrinks what you gave it, without changing what it is or how it looks. Every picture shows you what it will weigh before you save, and that figure is the real one.
Makes an app icon in one go
One picture in, a finished icon file out, with every size a Mac needs already inside it.
Hits a size limit for you
Told it has to come in under 500 KB, it works out how to get there. Handy when a website or a form will not take anything bigger.
Takes the private bits out
A photo carries where you took it, when, and on what. You can have all of that removed before you send it to anyone.
Drag the results straight out
Pull the finished files out of the window and into an email, a message, or a folder. No hunting for them afterwards.
The rest stays out of the way
Behind one Options button there is a quality slider, a switch to take the private details out of a photo, black and white, and buttons to turn or flip everything at once. It stays shut until you press it, and whatever you set there can become the way it always opens.
You can also just give it a number. Tell it the file has to come in under 500 KB and it works out the rest.
In from almost anything, out to what you need
An SVG to a PNG is the one everyone ends up on a website for, and it is the one this was built for. The rest came along with it.
What you can put in
Photos from your phone or your camera, screenshots, logos, PDFs, artwork from a design app, and the big raw files a proper camera makes. The list is your Mac’s rather than ours, so the rule is simple: if your Mac can open it, so can this.
What you can get back
The everyday ones, plus WebP and AVIF if you are putting pictures on a website, and finished icon files if you are making an app. This list comes from your Mac too, so a newer macOS quietly adds to it.
The ones people come looking for
A page each, with the steps for that job and what the app actually does to those particular bytes.
The ones worth answering straight
Why not just use one of the converter websites?
You can, and they mostly work. But you are handing your file to somebody else’s server to do it, which is a strange thing to do with a client’s logo or a photo of your kids. They also tend to do one file at a time, cap the size, and wrap the whole thing in adverts. This does the same job in a drag and a click, offline, however many files you have.
Is it really free?
Yes. No trial, no subscription, nothing locked, no adverts, and no account to make. Edmund is the app I charge for. This one I just wanted to exist.
What do I need to run it?
A Mac running macOS 15 Sequoia or later, with an Apple chip in it: an M1 or newer, so late 2020 onwards. There is no Intel build, and Apple carried on selling Intel Macs until 2023, so if you are not sure, the Apple menu and then About This Mac will tell you.
Do my photos get uploaded anywhere?
No. Nothing you drop in is ever sent anywhere, and that goes for the app and for the converters built into these pages. Three separate things worth keeping apart, since this site does ask you about cookies: the app reports nothing at all, with no account, no tracking and no crash reporting, so there is nothing to switch off. This website counts which pages get read, and only if you accepted the banner. The converters add one thing to that and nothing else, which is that a conversion happened. Never your file, its name or its size. One honest footnote, since anyone can check: the App Store version does ask macOS for permission to use the network. That is not so it can send anything, and it never does. It is because the part of macOS that draws the more complicated SVGs refuses to start without it.
Will it ruin the picture?
Left alone it will not: it makes the file smaller without touching how it looks. If you ask for something smaller or lower quality, it does what you asked, and it always shows you the result before you save.
There are two downloads. Which one?
Take the App Store one unless you have a reason not to. They are the same app. The App Store version follows Apple’s rules, so the first time it saves a file next to one of yours, or over one, it asks you to confirm the folder. The one from here skips that and keeps itself up to date on its own.
What can’t it do?
It does not crop, retouch, or paint, and it is not a photo library. It changes whole batches of pictures in one go. Anything you would want a brush for belongs somewhere else.
Weighing it up against something you already use? There is a longer look at how it compares to online converters, to Preview and Quick Actions and to ImageOptim, including the jobs each of those still does better.
There is a person behind this rather than a company: Will Wilson, on my own, in England. The app is signed and notarised by Apple, which is the check macOS runs on anything you download before it will open it.
“Lightning fast, great output quality, and the overwrite feature keeps my desktop clutter-free. It’s already earned a permanent spot in my dock.”
Rob ShawSenior Digital Designer, Think Digital GroupFor anyone who wants to know how
You can skip all of this. None of it changes how the app is used and none of it is something you have to decide. It is here because I would want to read it.
The encoders are the real ones
mozjpeg for JPEG, Google’s libwebp for WebP and libdeflate for PNG, all compiled in rather than shelled out to. A JPEG that only needs shrinking is rebuilt from the coefficients it already has, so not a single pixel changes.
The alpha channel nothing was using
Design tools write a transparency channel into PNGs that are completely opaque, and it costs about a quarter of the file. If every pixel in yours is opaque, that channel goes. Every pixel is checked, because 254 is not opaque.
PNG filtering is searched, not assumed
Most PNG writers pick their per-row filters with the same thirty-year-old heuristic. This one tries them and keeps whichever compresses smallest, which on flat graphics and screenshots is usually no filtering at all.
It never hands back a bigger file
If the optimised version comes out larger than what you gave it, which happens on files that have already been through an optimiser, it keeps yours.
A vector stays a vector
SVGs and PDFs are not rasterised on the way in. They are held as vectors until the final pixel size is known and rendered at exactly that, which is how one SVG produces seven crisp icon sizes rather than seven scaled copies of one.
The estimates are real encodes
The size on each card is not modelled. The file is genuinely encoded, cached, and re-encoded when you change a setting. The number you see is the number you get.
The format lists come from macOS
Both lists are read from the system at runtime rather than typed out, so a codec that arrives with a future macOS appears without an update, and an older macOS simply offers a few fewer. Measured on macOS 26.5 it is 62 formats in and 21 out. The two exceptions are SVG and PDF, which macOS will not read as images at all, so the app reads those itself.
What “remove metadata” actually removes
GPS, camera, timestamps and comments all go. macOS insists on writing a small Exif block containing the colour space and the pixel dimensions, and that cannot be suppressed, so this is not the same as a file with no metadata at all. The colour profile is always kept on purpose: a picture without one is a picture whose colours are a guess.
Apple silicon only, and macOS 15 or later
The compression libraries carry hand-written Apple silicon assembly, and Apple has finished with Intel, so there is no Intel build and there will not be one. The macOS floor is Sequoia rather than Tahoe: the only thing in the app that needed the newer system was a piece of toolbar styling that has nothing to style on an older one.
The difference between the two builds
Same code. The App Store build runs in Apple’s sandbox, which is why it asks permission before writing beside a file you dropped in, or over one. The direct build is signed with a Developer ID, is not sandboxed, and updates itself through Sparkle.
Why the App Store build asks for network access
Complicated SVGs, the ones with masks or filters in them, are drawn by WebKit, the same engine Safari uses. Inside Apple’s sandbox WebKit will not start at all unless the app holds the network entitlement, even though nothing is being loaded from anywhere. So the app holds it and never opens a connection. The direct build is not sandboxed and does not need it.
Why the App Store build asks for a folder when you replace originals
Apple’s sandbox lets the app into each file you drop in, but not into the folder that file sits in, and replacing a file means saving the new one into that folder before the old one goes to the Trash. So the first time you replace files you dropped in one by one, the App Store build asks for their folder, once, and remembers it. Drag in the folder itself and it has that already, so it does not ask. The direct build is not sandboxed and never asks.
Free, on both counts.
It costs nothing and it asks nothing of you. No account, no email, nothing uploaded. Two ways to get it: the Mac App Store, or straight from here.
macOS 15 or later. Apple silicon Mac. Version 1.1.0, out 11 October 2026. What’s new.
Something not working, or an idea for it? Tell me.