Image FAQs

🌄 Original Images

What access permissions do you require for our original images?

We only need read access to your original image storage. We fetch originals for processing but never write or modify them. You retain full control over your high-quality originals.

What happens to my original images?

We only fetch originals for processing; we never modify them. You retain your originals under your control.

What is the price for fetching the original images?

There is no charge for fetching original images from your source.

I store my originals in Amazon S3. Will I be charged by Amazon each time I fetch?

We cache your original image locally after the first fetch. If a 1 MB image is resized three times, you’re only charged by S3 once (1 MB transfer + 1 request). Subsequent resizes use our cache.

Can I store my original images with Gumlet?

No. We don’t provide storage. Use any object storage (e.g., S3, GCS, DigitalOcean Spaces). You retain full control and avoid vendor lock-in.

What happens if my original image is modified?

We cache your original for up to 3 months. Even if you update the source, our cache serves the old version until you clear it via dashboard or API.

What happens if my original image is deleted?

After deletion, until cache expiry (max 3 months), we serve the cached version. If we need to revalidate after deletion, requests return a 404. Flushing cache immediately will also cause a 404.

Do you support serving images from Google Drive?

No. Use an object storage service (e.g., Google Cloud Storage) to serve your originals.

Is there any limit on the input file?

Maximum input dimensions: 8192 × 8192 pixels.

What input image formats are supported?

See full list under Input Formats.

What happens when my original image is not found? Do my users see a broken image?

By default, we return 404, and your users may see a broken image. You can configure a fallback image in source settings to serve as an alternative.

How to setup S3 Image Source?

Here is the document for S3 integration - AWS S3 Setup. Alternatively, you can watch this video.

🌅 Output Images

How are processed images stored?

Processed images are cached in our system and in the CDN cache. Once generated, they’re delivered without extra processing time.

What is the maximum output image size?

Maximum output dimensions: 8192 × 8192 pixels.

What output formats are supported?

See full list under Output Formats.

Does Gumlet automatically remove EXIF metadata?

Yes—unnecessary EXIF data is removed from processed images. Originals remain untouched. To preserve metadata, enable the metadata parameter.

🔗 Integration & Setup

How to set up a custom domain?

Watch our video tutorial:

What is the impact of adding JavaScript on my page load time?

Our JS plugin is just 6 KB, loads in < 50 ms via async. It won’t block your page load.

How to optimize images served via CSS background?

Remove background-image in CSS. Instead, add data-bg="URL" and let our library load the correctly sized background. See set image as background.

Does Gumlet handle lazy loading? Should I use a third-party library?

Gumlet.js supports lazy loading—no need for external libraries. Learn more in lazy load images.

Can I serve images from multiple sources?

Yes. Create multiple sources in the dashboard and configure Gumlet.js to point to each domain. See load images from multiple domains.

Can I serve CSS / JS / other files through Gumlet?

Yes. Non-image files pass through unmodified via our CDN.
Example:

Store https://example.com/css/main.css in a “web folder” source.
Serve as https://example.gumlet.com/css/main.css.

🔍 SEO

Can serving images from Gumlet CDN be SEO-negative?

No—it's actually beneficial. We mark images as originating from your site via HTTP headers, so search engines attribute them to you.
Learn more:

🗄 Caching

How long are my images cached?

Originals: up to 90 days
Processed: up to 100 days

Is there any way to modify browser cache time?

Yes. Default: 100 days. Change it in Cache Management on the source.

Is there any way to modify CDN cache time?

Not generally recommended. Contact support if you must adjust CDN TTL.

What is the default cache time for errors?

Errors are cached for 5 minutes by our CDN. Enterprise customers may request longer TTL via support.

🛠️ Platform Compatibility

WordPress / WooCommerce

Yes—install our WordPress plugin to get started in minutes.

Shopify

Not currently supported—Shopify’s Liquid theme makes per-image integration infeasible.

Magento

Supported. Follow our Magento integration guide.

Django, Laravel, Angular, Rails, etc.

Use Gumlet.js (our JS plugin). See Getting started guide.

Webflow, Wix, Squarespace, Weebly

Not supported yet. We’ll consider plugins if demand grows.

💳 Payment

What currencies are supported?

Payments accepted in USD. Other currencies convert at the prevailing exchange rate.

Are my payment details secure?

We use Stripe to process and store payment details—your card data never touches our servers.

When do you charge my credit card?

Invoices are generated on the 1st of every month. If you have a saved card, it’s charged that day.

💵 Pricing

How is the bandwidth charge calculated?

You’re billed per GB for CDN data transferred beyond your plan. No separate fees for requests, transformations, caching, or storage.
Learn more: Gumlet Pricing