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 images from your original bucket or server. We won't need any
There is no charge for fetching original images from your image source.
I am storing my original images in Amazon S3. Will I get charged by Amazon each time you fetch the original image?
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 only 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 storage 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 images. You need to clear cache through the dashboard or API to reflect the change in your original image.
We cache your original image for a maximum of 3 months. If we need to revalidate the original image, it will start throwing a 404 error. If you flush the cache after deleting the original image, then we will start throwing a 404 error for that image.
We support an input image that is a maximum of 8192x8192 pixels.
You can find details about input image formats here: input formats
By default, we will return a 404 error when the image is not found and your users may see a 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 a broken image.
We store processed images in our cache. The processed images are also stored in the CDN cache. This ensures that if an image is already generated, no extra time is spent delivering them.
We support a maximum output image size of 8192 x 8192 pixels.
You can find details about output image formats here: 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: metadata
No, it will be actually beneficial. Your 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 the 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 a 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 the 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 an enterprise plan, you can contact support to modify the same.
async method. This ensures 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
data-bg attribute with image URL. Our library will ensure correct-sized background image will be loaded. You can find more information about it here: set image as background
Gumlet library is able to handle lazy loading. We recommend that you remove any third-party library and rely on our library for lazy-loading. Check more about enabling lazy loading here: lazy load images
Yes. You can serve images from as many different sources as you want. You just need to create multiple sources in the Gumlet panel and configure the Gumlet.js to load different images from different domains. A detailed example is given here: load images from multiple domains
Yes! You can serve all kinds of files from our service. If we detect non-image files, we will not process them but we will directly deliver them through our CDN. You get the 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 set up a web folder source with a Base URL of
https://example.com. After you set up the 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.
We accept payments in USD. If you are paying from any other currency you will be charged as per the equivalent exchange rate.
Absolutely! We use https://www.stripe.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 an invoice on the 1st of every month. If you have a credit card saved, it will be charged on the same day.
Yes! We have a WordPress plugin that can be installed and you can get started in minutes.
Our WordPress plugin will work just fine with your WooCommerce store.
We currently don't support Shopify stores. We tried our best but it is not possible to integrate with Shopify without changing every image tag in the liquid theme.
We do support optimizing images on Magento. Please follow this simple guide to start serving optimized images.
We don't support optimizing images for the above platforms. We will keep these in our mind though and if there is huge demand, we will be publishing plugins when needed.
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 a number of requests, a number of transformations, caching, or storage.
We have committed to using a contract 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 the same price across the globe so you can enjoy a very predictable pricing structure.
It's a simple marketing model where you can refer Gumlet and earn commission on sales from any user who subscribes to any paid Gumlet plan.
There is no limit on your revenue. You can earn 30% of all the payments made in the 1st year and 15% for all subsequent years.
You can simply login to your affiliate account received via email at any time and track all of your earnings.
Affiliate commissions are paid monthly, on the 10th of the month.
All affiliate commissions are paid via Paypal.
We will process all payouts greater than 1$ in the immediate cycle.
Updated over 1 year ago