We only need
read access to your original image storage. We only fetch original images for processing them but we don't write or modify any image. You retain all your high quality original images as it is under your control.
We only need access equivalent to
read. We must be able to fetch image from your original bucket or server. We won't need any
There is no charge for fetching original images from your image source.
We always cache your original image in our local cache after fetching it for the first time. This means if your 1 MB image is resized 3 times, you will onluy be charged by Amazon S3 for 1 MB data transfer and 1 single request. Subsequent resize operation will be performed on the cached image.
We don't support image storage. You can choose any file storage service like Amazon S3, Google Cloud Storage, DigitalOcean Spaces or any other stroage of your choice. This way, you also retain full control over your original images and won't have to suffer from vendor lockin.
We cache your original image for 3 months so we will still keep serving cached image. You need to clear cache through the dashboard or API to reflect change in your original image.
We cache your original image for maximum of 3 months. If we need to revalidate the original image, it will start throwing 404 error. If you flush the cache after deleting original image, then we will start throwing 404 error for that image.
We support input image which is maximum 16384x16384 pixels.
You can find details about input image formats here: https://docs.gumlet.com/developers/api-reference#input-formats
By default, we will return 404 error when image is not found and your users may see broken image. You can configure a fallback image in your source settings. If that image is set, we will display that image instead of showing broken image.
We store processed images in our cache. The processed images are also stored in CDN cache. This ensures that if image is already generated, no extra time is spent delivering them.
We suppot maximum output image size of 8192 x 8192 pixel.
You can find details about output image formats here: https://docs.gumlet.com/developers/api-reference#output-formats
Yes, we remove all unnecessary EXIF metadata from processed images. Your original images however are untouched so all that metadata is always present there. If you want to keep the metadata from original images in output images as well, you can check this parameter: https://docs.gumlet.com/developers/api-reference#metadata
No, it will be actually beneficial. You images are marked as originating from your website via HTTP headers sent by our system. Search engines look at that header and will associate those images with your website even if the URL is pointing to Gumlet.
We instruct search engines about location of original images so they always attribute your image to your site rather than attributing it to our CDN. You can read more about that in this article and this Google documentation.
We cache your original images for maximum of 90 days and processed images for 100 days.
Yes, we support modifying browser cache time. It's set at 100 days by default but you can change it in cache management section of the source.
We generally don't recommend modifying CDN cache time but if you must do it, please contact our support and we will be able to guide you.
All errors are cached by our CDN for 5 minutes. That means, if an error comes, it will be served from cache for the same user from cache for 5 minutes before revalidating the resource again. If you are on enterprise plan, you can contact support to modify the same.
async means it never becomes a roadblock in page-load.
In short, you should not even notice any impact on page load time due to our plugin.
You need to remove the CSS
background-image property and you need to set
Yes! You can serve all kinds of files from our service. If we detect non-image file, we will not process them but we will directly deliver them through our CDN. You get advantage of fast delivery of those files and reduced latency.
How do you serve these files? Simple, you just serve them the same way you serve images. For example, if your CSS file is stored at
https://example.com/css/main.css you need to setup a web folder source with a Base URL of
https://example.com. After you setup source, you can serve the CSS file like
https://example.gumlet.com/css/main.css It's that simple and your CSS file will now be delivered by our CDN.
No. You can use our service for free until you cross 1 GB free limit. Once you cross the limit, we will send you invoice with payment link at end of the month.
We recommend that you enable Auto-Pay and add credit card when you start using service. That will ensure uninterrupted service and you never have to worry about payment.
We accept payments in USD. If you are paying from other country, you will be charged as per equivalent exchange rate.
Absolutely! We use https://razorpay.com to store your payment information and process payments. None of your credit card details are received or stored on our servers.
We will send you invoice on 2nd of every month. If you have enabled Auto-Pay, your card will be charged on 3rd.
We calculate bandwidth as the amount of data transferred from our CDN to your users. If your image bandwidth was 10 TB before you switched to Gumlet and it becomes 6 TB after the switch, you will only be charged for 6 TB by us.
There is no extra charge for number of requests, number of transformations, caching or storage.
We don't charge any amount if your usage is zero in given month or you have only used the bandwidth from free tier. Our charge is however $1 per 10 GB usage so if you use our service in a month, you will be charged minimum $1.
We have committed use contracts with CloudFront which reduces per GB pricing of CloudFront for us. We serve more than 100 TB images in a month and hence enjoy lower per GB pricing. Rather than beefing our profit margins, we chose to pass it on to our customers.
We also provide same price across the globe so you can enjoy very predictable pricing structure.