Public | Automated Build

Last pushed: 9 months ago
Short Description
A caching, resizing image proxy written in Go
Full Description


imageproxy is a caching image proxy server written in go. It features:

  • basic image adjustments like resizing, cropping, and rotation
  • access control using host whitelists or request signing (HMAC-SHA256)
  • support for jpeg, png, webp (decode only), and gif image formats (including animated gifs)
  • on-disk caching, respecting the cache headers of the original images
  • easy deployment, since it's pure go

Personally, I use it primarily to dynamically resize images hosted on my own
site (read more in this post). But you can also enable request signing and
use it as an SSL proxy for remote images, similar to atmos/camo but with
additional image adjustment options.

URL Structure

imageproxy URLs are of the form http://localhost/{options}/{remote_url}.


Options are available for resizing, rotation, flipping, and digital signatures
among a few others. Options for are specified as a comma delimited list of
parameters, which can be supplied in any order. Duplicate parameters overwrite
previous values.

See the full list of available options at

Remote URL

The URL of the original image to load is specified as the remainder of the
path, without any encoding. For example,

In order to optimize caching, it is recommended that URLs not contain query


The following live examples demonstrate setting different options on this
source image
, which measures 1024 by 678 pixels.

Options Meaning Image
200x 200px wide, proportional height <a href=""><img src="" alt="200x"></a>
0.15x 15% original width, proportional height <a href=""><img src="" alt="0.15x"></a>
x100 100px tall, proportional width <a href=""><img src="" alt="x100"></a>
100x150 100 by 150 pixels, cropping as needed <a href=""><img src="" alt="100x150"></a>
100 100px square, cropping as needed <a href=""><img src="" alt="100"></a>
150,fit scale to fit 150px square, no cropping <a href=",fit/"><img src=",fit/" alt="150,fit"></a>
100,r90 100px square, rotated 90 degrees <a href=",r90/"><img src=",r90/" alt="100,r90"></a>
100,fv,fh 100px square, flipped horizontal and vertical <a href=",fv,fh/"><img src=",fv,fh/" alt="100,fv,fh"></a>
200x,q60 200px wide, proportional height, 60% quality <a href=",q60/"><img src=",q60/" alt="200x,q60"></a>

Transformation also works on animated gifs. Here is this source
resized to 200px square and rotated 270 degrees:

<a href=",r270/"><img src=",r270/" alt="200,r270"></a>

Getting Started

Install the package using:

go get

(Note that go1.2 and earlier may have trouble fetching the package with go get).

Once installed, ensure $GOPATH/bin is in your $PATH, then run the proxy


This will start the proxy on port 8080, without any caching and with no host
whitelist (meaning any remote URL can be proxied). Test this by navigating to
http://localhost:8080/500/ and
you should see a 500px square coder octocat.


By default, the imageproxy command does not cache responses, but caching can be
enabled using the -cache flag. It supports the following values:

  • memory - uses an in-memory cache. (This can exhaust your system's
    available memory and is not recommended for production systems)
  • directory on local disk (e.g. /tmp/imageproxy) - will cache images
    on disk
  • s3 URL (e.g. s3:// - will cache
    images on Amazon S3. This requires either an IAM role and instance profile
    with access to your your bucket or AWS_ACCESS_KEY_ID and AWS_SECRET_KEY
    environmental parameters set.

For example, to cache files on disk in the /tmp/imageproxy directory:

imageproxy -cache /tmp/imageproxy

Reload the codercat URL, and then inspect the contents of
/tmp/imageproxy. Within the subdirectories, there should be two files, one
for the original full-size codercat image, and one for the resized 500px

Referrer Whitelist

You can limit images to only be accessible for certain hosts in the HTTP
referrer header, which can help prevent others from hotlinking to images. It can
be enabled by running:

imageproxy  -referrers

Reload the codercat URL, and you should now get an error message. You can
specify multiple hosts as a comma separated list, or prefix a host value with
*. to allow all sub-domains as well.

Host whitelist

You can limit the remote hosts that the proxy will fetch images from using the
whitelist flag. This is useful, for example, for locking the proxy down to
your own hosts to prevent others from abusing it. Of course if you want to
support fetching from any host, leave off the whitelist flag. Try it out by

imageproxy -whitelist

Reload the codercat URL, and you should now get an error message. You can
specify multiple hosts as a comma separated list, or prefix a host value with
*. to allow all sub-domains as well.

Signed Requests

Instead of a host whitelist, you can require that requests be signed. This is
useful in preventing abuse when you don't have just a static list of hosts you
want to allow. Signatures are generated using HMAC-SHA256 against the remote
URL, and url-safe base64 encoding the result:

base64urlencode(hmac.New(sha256, <key>).digest(<remote_url>))

The HMAC key is specified using the signatureKey flag. If this flag
begins with an "@", the remainder of the value is interpreted as a file on disk
which contains the HMAC key.

Try it out by running:

imageproxy -signatureKey "secret key"

Reload the codercat URL, and you should see an error message. Now load a
signed codercat URL and verify that it loads properly.

Some simple code samples for generating signatures in various languages can be
found in URL Signing.

If both a whiltelist and signatureKey are specified, requests can match either.
In other words, requests that match one of the whitelisted hosts don't
necessarily need to be signed, though they can be.

Run imageproxy -help for a complete list of flags the command accepts. If
you want to use a different caching implementation, it's probably easiest to
just make a copy of cmd/imageproxy/main.go and customize it to fit your
needs... it's a very simple command.

Default Base URL

Typically, remote images to be proxied are specified as absolute URLs.
However, if you commonly proxy images from a single source, you can provide a
base URL and then specify remote images relative to that base. Try it out by

imageproxy -baseURL

Then load the codercat image, specified as a URL relative to that base:
http://localhost:8080/500/images/codercat.jpg. Note that this is not an
effective method to mask the true source of the images being proxied; it is
trivial to discover the base URL being used. Even when a base URL is
specified, you can always provide the absolute URL of the image to be proxied.

Scaling beyond original size

By default, the imageproxy won't scale images beyond their original size.
However, you can use the scaleUp command-line flag to allow this to happen:

imageproxy -scaleUp true

WebP support

Imageproxy can proxy remote webp images, but they will be served in either jpeg
or png format (this is because the golang webp library only support decoding)
if any transformation is requested. If no format is specified, imageproxy will
use jpeg by default. If no transformation is requested (for example, if you
are just using imageproxy as an SSL proxy) then the original webp image will be
served as-is without any format conversion.


You can build and deploy imageproxy using any standard go toolchain, but here's
how I do it.

I use goxc to build and deploy to an Ubuntu
server. I have a $GOPATH/ file
which limits builds to 64-bit linux:

   "ConfigVersion": "0.9",
   "BuildConstraints": "linux,amd64"

I then run goxc which compiles the static binary and creates a deb package at
build/0.2.1/imageproxy_0.2.1_amd64.deb (or whatever the current version is).
I copy this file to my server and install it using sudo dpkg -i imageproxy_0.2.1_amd64.deb, which is installed to /usr/bin/imageproxy.

Ubuntu uses upstart to manage services, so I copy
etc/imageproxy.conf to /etc/init/imageproxy.conf on
my server and start it using sudo service imageproxy start. You will
certainly want to modify that upstart script to suit your desired


It's easy to vendorize the dependencies with Godep and deploy to Heroku. Take
a look at this GitHub repo


A docker image is available at willnorris/imageproxy.

You can run it by

docker run -p 8080:8080 willnorris/imageproxy -addr

Or in your Dockerfile:

ENTRYPOINT ["/go/bin/imageproxy", "-addr"]


You can use follow config to prevent URL overwritting:

  location ~ ^/api/imageproxy/ {
    # pattern match to capture the original URL to prevent URL
    # canonicalization, which would strip double slashes
    if ($request_uri ~ "/api/imageproxy/(.+)") {
      set $path $1;
      rewrite .* /$path break;
    proxy_pass http://localhost:8080;


imageproxy is copyright Google, but is not an official Google product. It is
available under the Apache 2.0 License.

Docker Pull Command
Source Repository