ImageEngine is an independent, global image CDN that automatically serves your users the leanest, greenest, fastest, and best-looking images regardless of device, browser, or network speed.
A collection of resources for promotion of the ImageEngine Developer Program
Website | imageengine.io |
Github | github.com/imgeng |
Documentation | support.imageengine.io |
ImageEngine Control panel | control.imageengine.io |
Twitter/X | @imagecdn |
ImageEngine Affiliate Program | imageengine.io/affiliate-program-apply |
We will be launching the ImageEngine Developer program this winter. We'll be using ProductHunt as a launch platform and the final launch date will be set later.
Before the launch is scheduled, we want to build an audience. The audience is collected in two different ways:
We'll also offer early access to the ImageEngine Developer program for selected users. Users can sign up for a preview/beta of the Developer Program here: https://control.imageengine.io/register/dev
The Developer program includes a free ImageEngine account. No credit card is required.
However, since it's free, there are some limitations:
ImageEngine works like most other CDNs by connecting an image origin (HTTP or S3) to a public delivery address. This mapping is called an "Engine". Images are served from the delivery address.
Example:
Your website is https://www.foo.com
, and your images are located on that host (origin), then your html may look like this: <img src="https://www.foo.com/image.jpg">
.
Next, assuming that the Engine configured with www.foo.com
as origin, has this delivery address xyz.dev.cdn.imgeng.in
, then your updated <img>
references will look like this: <img src="https://xyz.dev.cdn.imgeng.in/image.jpg">
Some demos:
(More samples below)
Once a delivery address is obtained, ImageEngine is ready to optimize images. This can be done in "auto mode" or by the use of URL directives.
Auto mode is where you simply provide the url to the image as it is on your website: <img src="//try.cdn.imgeng.in/img/bread.png">.
In this case, ImageEngine will do its best effort in optimizing based on the information available.
You may also use URL directives: <img src="//try.cdn.imgeng.in/img/bread.png?imgeng=/w_300/f_webp">
. URL directives are instructions to ImageEngine on how to optimize the image. For example, size, format, corps, rotation, etc.
An additional handy feature is that ImageEngine can take any image URL and optimize it by prefixing it with the delivery address: <img src="//try.cdn.imgeng.in/http://jelly.com/img/bread.png">
. Useful for testing multiple origins.
Engines, settings, configuration, and statistics are available at control.imageengine.io
Here is a quick overview of the features of the control panel:
By adding a request header (with a browser plugin, command line with curl etc) ImageEngine will respond with additional information about the image. This is handy when debugging images and learning how they are optimized.
ImageEngine already supports JPEG XL and AVIF.
Due to poor performance, AVIF is not enabled by default.
JPEG XL is currently enabled for PNG orign images, but full support will be rolled out shortly. Meanwhile, JPEG XL can be enabled manually.
As the only Image CDN, we're proud to have the best support for Client Hints. In addition to width
, viewport-width
and dpr
ImageEnigine also supports ect
and save-data
.
With ImageEngine all image traffic is carbon neutral. We're committed to reducing the carbon footprint of ImageEngine.
80% less bytes means 80% less emissions (rule of thumb). Read more here
Also worth noting is our support for carbon.txt
To make integration with real-life projects easier, several plugins are available:
Support via front-end dev frameworks and the Gatsby native support.
Support via front-end dev frameworks and the Gatsby native support.
Support via front-end dev frameworks and the Gatsby native support.