Cover Resize Tutorials

Check our cover resize examples. rethumb can resize an image to cover any dimensions:

Cover resize now Available

Our new operation cover is now available. This feature allows you to resize an image to any dimension: upscaling, downscaling and cropping as needed.

An example, if you have an image with dimensions 300 x 300 px you can use the following request to get a new 150 x 200 px image:

https://api.rethumb.com/v1/cover/150x200/format/jpg/http://images.rethumb.com/image_coimbra_300x300.jpg

Original image

As you can see the new image itseft have no distortion in any way:

Transformed image

This feature is very similiar to CSS background cover, you can read more about it here: CSS3 background-size Property.

Check our API for more details on how to use this new transformation.

WebP Support now Available

Support for WebP images in now available. You can use rethumb to convert WebP images to other formats like JPG or PNG and vice-versa.

Convert from WebP to JPG:

https://api.rethumb.com/v1/square/250/format/jpg/http://images.rethumb.com/image_coimbra_999x999.webp

Convert from JPG to WebP:

https://api.rethumb.com/v1/square/250/format/webp/http://images.rethumb.com/image_coimbra_999x999.jpg

Format Conversion Tutorials

Check our format conversion examples. rethumb can convert to and from JPG, GIF, PNG, TIFF and WebP:

Format Conversion now Available

Starting today our format conversion feature is available for all our customers.

This feature allows you to convert from an image file format to another. At the moment we can convert from and to JPG, GIF, PNG, TIFF and WebP.

The following example will convert a JPG image to GIF, PNG and WebP. Note that the format feature must be used with other transformation operation like height, square or width.

http://api.rethumb.com/v1/height/250/format/gif/http://images.rethumb.com/image_coimbra_300x300.jpg
http://api.rethumb.com/v1/square/250/format/png/http://images.rethumb.com/image_coimbra_300x300.jpg
http://api.rethumb.com/v1/width/250/format/webp/http://images.rethumb.com/image_coimbra_300x300.jpg

Documention on this feature is online at http://rethumb.com/api.

It is a paid feature so you’ll need to subscribe to a paid plan. Check our prices at http://rethumb.com/pricing.

Any question contact us at [email protected].

WebP Support

rethumb will start supporting WebP images soon. WebP is the Google image format for the web.

From their site:

“WebP is a new image format that provides lossless and lossy compression for images on the web. WebP lossless images are 26% smaller in size compared to PNGs. WebP lossy images are 25-34% smaller in size compared to JPEG images”

You can read more about it at https://developers.google.com/speed/webp/?hl=en

Not many browsers support this tecnology: http://caniuse.com/#search=webp. Be careful when sending WebP images to your clients.

Format Conversion

We are preparing a new feature for rethumb: format conversion.

At the moment our API creates images with the same image format as the input.
E.G.: PNG images are converted to PNG thumbnails, etc.

This new feature will allow our users to select the output format.
In that way it’ll be possible to convert PNG images to JPG thumbnails, etc.

Our API will support conversion from PNG, JPG, GIF, TIFF and WEBP to PNG, JPG, GIF, TIFF and WEBP.

New HTTP Header: access-control-allow-origin

We have added a new HTTP header to our API responses:

access-control-allow-origin: *

This header will allow you to call our service from any domain. We had this header in place for JSON requests but it is available for all types of requests.

You can read more about Access Control Allow Origin at HTTP access control (CORS).


HTTP response headers for successful requests (status code 200):

HTTP/1.1 200 OK
Content-Type: image/jpeg
Etag: d16c7a75b11ea555016afb2b3655cb870b32df4c
access-control-allow-origin: *
Cache-Control: max-age=2592000
Strict-Transport-Security: max-age=15768000

HTTP response headers for cached requests (status code 304):

HTTP/1.1 304 Not Modified
access-control-allow-origin: *
Cache-Control: max-age=2592000
Strict-Transport-Security: max-age=15768000

HTTP response headers for errors (status code 400):

HTTP/1.1 400 Bad Request
Content-Type: image/png
rethumb-error-message: Square must be numeric. (#701)

Short-term Roadmap

This post presents rethumb’s short-term roadmap. These features are a mix of user requests and in-house ideas given the usage of our service. We expect to start working on them by January.

In the next few days we’ll add a new blog entry with details on the new API operations: convert and qualilty.


CNAME Records Support

This feature will allow the usage of your domain as an alias to our api.rethumb.com so that you can keep your brand while using our service.

More about CNAME here: https://en.wikipedia.org/wiki/CNAME_record


Default Images for Errors

When our service finds an error, while processing a request, it sends an image with the error message (and a HTTP header with the same message).

rethumb error response

Our idea is to allow the user to setup a default image that our service will send in place of the black box with the error. This could be useful to hide errors from your users and give them a less disruptive experience.


Allow Paths in Sources

At the moment when you add a new source it can only be a domain or a sub-domain. With this feature you will be able to add a path:

  • domain.com/folder
  • sub.domain.com/folder/in

This can be used to limit access to your image sources with higher granularity.

E.G.: AWS S3 urls can be something like: https://s3.amazonaws.com/<your_folder>/. With this feature you will be able to limit your plan only to your folder on S3.


SLA for Paid Plans

We’ll start offering a SLA for our paid plans so that our users know what to expect from each plan. In order to provider a better service we are also implementing rate limiting on the number of new images processed by minute.

More on SLA: https://en.wikipedia.org/wiki/Service-level_agreement