On the forum I administer, I am forced to run a tight attachment policy. Disk space doesn’t grow on trees. Occasionally this leads to questions about the small attachment size limit of 50 KiB. This guide is intended to clarify that this is not nearly as tiny as you might think. Note that although I’ll mention commands without much explanation for the sake of brevity, you’re always recommended to further explore the possibilities offered by those commands with the
--help flag as well as by running
First you need to ask yourself what kind of file type is appropriate, if you have the choice. On screenshots, the main purpose of attachments on my forum, you’ll often encounter large areas of uniform background colors. PNG is therefore almost invariably the right choice. Crop out everything but what’s relevant. JPEG is appropriate for more dynamic pictures such as photographs. If you want to do a lot with photographs, you might want to consider an external hosting service. My wife likes SmugMug. Still, for thumbnails you might be able to do a fair bit more within a few hundred KiB than you might think. Finally, the vector graphics in SVG result in pictures that always look sharp. You’ll typically have drawn these in a program like Inkscape or Adobe Illustrator.
Table of Contents
- 1. Optimizing JPEG
- 2. Optimizing PNG
- 3. Optimizing SVG
- Addendum A: Scanned Documents
- Addendum B: Video
1. Optimizing JPEG
Often you’ll want to crop your file. Do not edit your JPEG followed by resaving it because this will result in reduced quality! You can crop losslessly with cropgui. On Windows you can use IrfanView.
If you don’t want to crop, and also potentially for some post-cropgui optimization, use
jpegtran -copy none -progressive -optimize file.jpg > file-opt.jpg. Note that this will get rid of all metadata, which may be undesirable. If so, use
jpegtran -copy all -progressive -optimize file.jpg > file-opt.jpg.
Of course if you want to scale down your JPEG there’s no point in mucking about with lossless cropping first. After scaling down, check how long your quality can go (also see a little helper script I wrote). In any case, you should avoid introducing any unnecessary compression steps with associated quality loss. Here are some results:
The original 11.jpg at 2.19 MB.
Losslessly cropped 11-crop.jpg at 1.11 MB.
-copy all -progressive -optimize11-crop-opt.jpg at 1.04 MB.
-copy nonewould’ve saved an extra whopping 40-some KiB, which on this kind of filesize has little benefit, and besides, I quite like the metadata. For thumbnail-sized files the balance is likely to be different. For example, the 52.2 KiB SmugMug auto-generated thumbnail below can be insignificantly reduced to 51.1 KiB with
--copy all, but to 48.2 KiB with
--copy none. I think an 8% reduction is not too shabby, plus it brings the file size down to under the arbitrary 50 KiB limit on my forum.
2. Optimizing PNG
As I wrote in the introduction, for screenshots PNG is typically the right choice. If you want to use lossless PNG, use
optipng -o7. In my experience it’s ever so slightly smaller than other solutions like
pngcrush. But as long as you use a PNG optimizer it shouldn’t much matter which one you fancy. Also see this comparison.
If you don’t care about potentially losing some color accuracy, use
pngquant instead. To top it off, if you really want to squeeze out your PNG, you can pass quality settings with
--quality min-max, meaning you can pass
--quality 30-50 or just
--quality 10. Here are some quick results for the screenshot in the SVG section below, but be sure to check out the pngquant website for some impressive examples.
$ du -h --apparent-size inkscape-plain-svg.png 27K inkscape-plain-svg.png $ du -h --apparent-size inkscape-plain-svg-fs8\ default.png 7.6K inkscape-plain-svg-fs8 default.png $ du -h --apparent-size inkscape-plain-svg-fs8\ quality\ 10.png 4.3K inkscape-plain-svg-fs8 quality 10.png
In this case there is no visual distinction between the original PNG and the default pngquant settings. The quality 10 result is almost imperceptibly worse unless you look closely, so I didn’t bother to include a sample.
3. Optimizing SVG
For using SVG on the web, I imagine I don’t have to tell you that in Inkscape, you should save your file as Plain SVG.
What you may not know is that just like there are lossy PNGs, you can also create what amounts to lossy SVGs. There are some command-line tools to optimize SVGs, including (partially thanks to this SO answer):
- Scour is probably the best command line tool for some quick optimization. You can just use the defaults like
scour < in.svg > out.svgor
scour -i in.svg -o out.svg. But I recommend you go further.
- SVGO (SVG Optimizer)
- SVG-optimiser (by Peter Collingridge)
- SVG-editor (by Peter Collingridge)
My personal preference for squeezing out every last byte goes toward the web-based version of the SVG-editor by Peter Collingridge. By running it in a browser with inferior SVG support such as Firefox, you’ll be sure that your optimized SVG still works properly afterward. The command line tools can only safely be used for basic optimizations, whereas the effects of going lossy (such as lowering precision) can only be fully appreciated graphically.
Addendum A: Scanned Documents
Scanned documents are a different item altogether. The best format for private use is DjVu, but for public sharing PDF is probably preferable. To achieve the best results, you should scan your documents in TIFF or PNG, followed by processing with unpaper or ScanTailor. If you’ve already got a PDF you’d like to improve, you can use pdfsandwich or my own readablepdf.
Addendum B: Video
I’m not aware of any lossless optimization for video compression such as offered by jpegtran, but you can often losslessly cut video. In the general purpose editor Avidemux, simply make sure both video and audio are set to copy. There is also a dedicated cross-platform app for lossless trimming of videos called, unsurprisingly, LosslessCut. If you do want to introduce loss for a smaller file size you can use the very same Avidemux with a different setting, ffmpeg, mpv, VLC, and so forth. You can get reasonable quality that’ll play many places with something like:
ffmpeg -i input-file.ext -c:v libx264 -crf 19 -preset slow -c:a libfaac -b:a 192k -ac 2 output-file.mp4
For the open WebM format, you can use something along these lines:
ffmpeg -i input.mp4 -c:v libvpx -b:v 1M -c:a libvorbis output.webm
More examples on the ffmpeg wiki. Note that in many cases you should just copy the audio using
-acodec copy, but of course that’s not always an option. Extra compression artifacts in audio detract significantly more from the experience than low-quality video.