Features Videos Help About Updates
Menu Buy Now

Optimizing Images

First Steps:
Getting Started
Live-Reload Browsers
Browser Sync
Set Language Options
Set Output Paths & Action
Second Steps:
Defaults For New Projects
Build Your Project
Set Target Browsers
Stuff To Know:
CodeKit + Git
Troubleshooting
License Recovery
PostCSS Tools:
Autoprefixer
PurgeCSS
Custom PostCSS Plugins
Other Tools:
npm
Babel — (JS Transpiler)
Terser — (JS Minifier)
Rollup — (JS Bundler)
Cache-Buster
HTML-Minifier
LightningCSS
Bless
Languages:
Sass
Less
Stylus
JavaScript
CoffeeScript
TypeScript
Pug
Haml
Slim
Kit
Markdown
JSON
Image Optimizers:
WebP
PNG
JPEG
SVG
GIF
Frameworks:
CodeKit Frameworks
Tailwind
Bootstrap
Bourbon
Bitters
Zurb Foundation
Susy
Nib
Jeet
Syntax Checkers:
ESLint
Advanced:
Hooks
Environment Variables
Adding Custom Languages
Team Workflows
Scripting CodeKit
Editor Plugins:
Nova
Atom
Sublime Text
Coda 2
More
Read-Only Mode
Upgrading From 2.0
FAQ

PNG, JPEG, and GIF

CodeKit losslessly optimizes PNG, JPEG, and GIF images using well-tested tools: PNGCrush, PNGQuant, JPEGOptim, and Gifsicle.

The Image Inspector

Select one or more images in CodeKit and you'll see the Image Inspector:

a screenshot of the image file inspector in the CodeKit window
Options

The Inspector Pane shows information about the selected image, including how much its file size has changed. Currently, no optimization options are exposed. CodeKit automatically uses the most aggressive settings that still provide lossless quality.

File Sizes Can Be Tricky

The initial size is how large an image was the first time CodeKit ever saw it. That value never changes. If you start with a small image, then overwrite it with a bigger one, it's possible that the current size may be larger than the initial size, even after optimization occurs. In this case, the initial size isn't really accurate. It was set when a smaller file occupied the current path.

Output Path & Action
a screenshot of the output path section of the image file inspector in the codekit window

These options apply to files of all types. They are explained in Setting Output Paths & Actions.

Normally, CodeKit will not copy or process a file if its output path is the same as its input path. The exception to this is images.


Why Don't I See Huge Reductions?

Modern image editors like Sketch and Photoshop are actually really good at writing pre-optimized files. In many cases, your images can't be further optimized without reducing quality.

What About Lossy Optimization?

Currently, all of CodeKit's optimizations are lossless. Lossy compression can achieve even smaller file sizes, but at the expense of image quality. Lossy optimization options are coming in an update, soon.

SVGs, Too

CodeKit can also optimize SVG files.

Made in San Diego, CA

Follow the Developer on Twitter

Email Support

Report a Bug

Privacy Policy