Business Proxy add-onPrivate beta

Many remote sources. One reliable image pipeline.

Smart Image Gateway sits between unpredictable third-party sources and your WebP Cloud Proxy, turning remote image URLs into a secure, observable origin for optimization and delivery.

Included at no additional add-on fee for qualifying Business Proxy deployments. Proxy usage remains metered under the agreed plan. Source names are compatibility examples and do not imply affiliation.

Unified Proxy outputimages.customer.commanaged CDN · your CDN · direct
Source policy engineSmart Image Gatewayverify · normalize · fetch · recover
Xiaohongshu*.xhscdn.com
SSPAIcdnfile.sspai.com
Pixivi.pximg.net
Weibo*.sinaimg.cn
Instagram*.cdninstagram.com
Generic HTTPpublic image URL
Attached toOne Business Proxy
Add-on feeIncluded when qualified
Metered atThe Proxy delivery layer
Remote images are different

A normal origin is yours. These origins are not.

A fixed bucket or website usually has one cache policy and one authentication model. Feed readers, communities, AI products, and publishing tools can encounter millions of URLs across sources with conflicting behavior.

Headers

One Referer does not fit every source.

Some origins require a known site Referer, some reject it, and others depend on a browser-like request profile.

Identity

A different URL is not always a different image.

Tracking parameters and reordered queries can multiply cache keys, while signed source parameters must remain untouched.

Failure

Remote sources fail on their own schedule.

Timeouts, 429 responses, redirects, HTML error pages, and oversized files need bounded, source-aware recovery.

Who it is for

Products that render images they do not host.

Smart Image Gateway fits when the URL arrives inside someone else’s content. Your product is responsible for showing the picture. The same path also covers a community or CMS that embeds remote files in the pages it publishes.

RSS readersNewslettersDigest apps

Feed and newsletter readers

One article can contain images from the publisher, a CDN, and several social sources. The reader still has to show every picture on its own HTTPS origin, send the Referer each source expects, and keep the subscriber’s address off that request.

WeiboXiaohongshuPixivInstagram

Social and community clients

Posts from Weibo, Xiaohongshu, Pixiv, and Instagram often answer only when the request looks like their own site. A client that embeds those pictures needs a separate source policy for each host.

Link previewsRead-it-laterAI readers

Previews and reading tools

Link unfurls, read-it-later apps, and AI products illustrate pages the user did not upload. Unique URLs dominate, so normalization and stale-cache recovery matter as much as the first successful fetch. A CMS that embeds remote images has the same shape.

Source names describe compatibility examples only. Mention does not imply affiliation, endorsement, or that a named service runs on this add-on.

How a product calls it

Point the browser at the attached Proxy.

Your renderer stays in place. The browser, or your server, requests the WebP Cloud Proxy or custom image domain. The Proxy resolves the encoded source through Smart Image Gateway, then transforms, caches, and delivers the validated response.

Example

The browser requests your image domain.

Before the page reaches the browser, replace each remote src with an HMAC-authenticated route on images.customer.com. The public hostname belongs to the attached Proxy; Smart Image Gateway remains its controlled remote origin.

After ,b64/, use raw URL-safe Base64 without = padding. The HMAC-SHA256 covers the decoded original URL—not the encoded payload or normalized cache key.

referrerpolicy="no-referrer" keeps the reader page out of the public request. The Gateway applies its own source Referer and does not forward the visitor's address to the remote host.

The example uses the README's fixed change-me test vector for https://example.com/a.jpg. A real deployment uses a private secret, an agreed hostname, and the parameters supported by its Business Proxy.

In the readerProxy URL backed by the Gateway
<img
  src="https://images.customer.com/camo/89e46047076454f6460f9814e289f8d737ab90bf5fdfe4a21bab081eb4b641a0,b64/aHR0cHM6Ly9leGFtcGxlLmNvbS9hLmpwZw"
  alt="Remote article image"
  data-original-src="https://example.com/a.jpg"
  referrerpolicy="no-referrer"
>
Base64url payload
aHR0cHM6Ly9leGFtcGxlLmNvbS9hLmpwZw
Decodes to
https://example.com/a.jpg
01

Rewrite the markup

When you render the article, replace each remote src with an HMAC-authenticated URL on the attached Proxy or custom image domain. Keep the publisher address on data-original-src when the application needs it.

02

Use either route contract

Use /camo/{hmac},b64/{base64url} or /?url={base64url}&sig={hmac}. The payload is raw URL-safe Base64 without padding; width, format, and quality remain Proxy parameters.

03

Fetch from your server

Request the attached Proxy while you build a preview, digest, or notification. Web, mobile, and email then share your image domain, while the remote source sees only the managed fetch path.

One managed request path

Origin shielding before Proxy optimization.

The Gateway keeps a bounded cache of validated original bytes for source resilience. The attached WebP Cloud Proxy remains the product boundary for transformed variants, delivery cache, quota, domain, and customer-facing traffic.

  1. 01

    Remote URL

    One of many source domains enters through an HMAC-authenticated route.

  2. 02

    Smart Gateway

    Verify, guard, normalize, coalesce, fetch, validate, and keep an origin cache.

  3. 03

    WebP Cloud Proxy

    Resize, convert, watermark, cache delivery variants, and account for usage.

  4. 04

    Delivery

    Use managed delivery, place your CDN in front, or read directly.

What the add-on contributes

An origin shield for sources you do not control.

Normalize once, fetch once, reject dangerous payloads, and keep a known-good source available when an upstream becomes unreliable.

01

Source-specific fetch policy

Apply built-in Referer rules, a configurable browser-like request profile, safe query handling, and optional HTTP or SOCKS egress with direct-host exclusions.

02

HMAC and network safety

Authenticate the decoded source URL with HMAC-SHA256, allow only HTTP(S), block private and metadata networks, pin direct connections to an inspected IP, and re-check every redirect.

03

Image payload limits

Reject non-images, SVG, oversized responses, and dangerous declared dimensions before the attached Proxy attempts any pixel decoding or transformation.

04

Canonical origin shield

Normalize equivalent URLs, collapse known tracking variants, preserve signed-query hosts, combine concurrent misses, and keep validated source bytes in a bounded disk cache.

05

Failure containment

Retry transient transport and upstream failures, open a per-source circuit breaker, serve stale cached images when available, and fail closed when recovery is exhausted.

06

Bounded observability

Export Prometheus request, latency, byte, cache, stale, rejection, success-ratio, and circuit-state signals without allowing unbounded source labels.

Access
HMAC-SHA256
Network
HTTP(S) only
Default payload cap
80 MiB
Declared pixel cap
40 MP
Operations
Prometheus-ready
Keep the Proxy, choose the edge

Managed delivery is the default. Your CDN can still sit in front.

Smart Image Gateway remains attached to WebP Cloud Proxy in every mode. What changes is who owns the final cache and delivery path.

Default

WebP Cloud managed delivery

One managed path for source policy, transformation, cache, custom domain, and image delivery.

Gateway → Proxy → WebP Cloud delivery
By arrangement

Bring your own CDN

Keep the Gateway and Proxy as a controlled image origin while your CDN handles the final visitor-facing cache.

Gateway → Proxy → Your CDN
Controlled use

Direct Proxy output

Read from the authenticated Proxy without another downstream CDN for previews, back-office, or low-volume clients.

Gateway → Proxy → Application
Modeled high-cardinality workload

When almost every request is a new origin, the billing model matters.

This rounded example is based on historical production traffic from a feed-style workload. It is an illustration, not a named customer invoice.

≈12Mimage requests / month
≈5Munique source paths
≈0.75 TBmonthly output
<25%repeat cache hits
Unique-transform pricing

About $2.5k / month

At one unique transformation per source path, using Cloudflare Images' public price of $0.50 per 1,000 after the first 5,000. More variants can raise the count; URL normalization can lower it.

Check Cloudflare's current pricing
WebP Cloud managed solution

Gateway included. Proxy usage metered.

Source policy and recovery are provisioned with the qualifying Business Proxy. The quote is driven by Proxy request volume, cache, regions, and support—not a second retail product.

Model your workload with us

This model applies to Cloudflare Images transformations. A Worker-only fetch and cache path follows a different request and CPU pricing model. Estimates compare billing shapes, not feature-identical products. Cloudflare, Cloudflare Images, and related marks belong to their respective owners; compatibility or comparison does not imply affiliation.

Commercial model for the private beta

No separate Gateway SKU—for now.

We attach Smart Image Gateway to a qualifying Business Proxy when a workload genuinely needs multi-source remote fetching. That keeps one technical owner, one request path, and one metered delivery agreement.

Gateway add-on
$0 for qualifying deployments
Requests and delivery
Consumed by the attached Business Proxy
Custom source work
Scoped when a private adapter or egress setup is required
Questions, answered

Before you put remote URLs into production.

The private beta is intentionally scoped around high-volume Business Proxy workloads, not an unrestricted public endpoint.

Can I buy Smart Image Gateway on its own?

Not currently. It is provisioned as an add-on for selected WebP Cloud Business Proxy deployments, so every image still passes through an authenticated Proxy before delivery.

Does the Gateway resize or convert images?

No. The Gateway fetches and validates the original bytes without decoding pixels or re-encoding the image. Your WebP Cloud Proxy performs resize, format selection, quality changes, watermarking, variant caching, and delivery.

Can we keep our current CDN?

Yes, by arrangement. Your CDN can use the WebP Cloud Proxy as its authenticated image origin. The Gateway remains behind the Proxy, so source policy and transformation behavior stay consistent.

Is this a public URL proxy?

No. WebP Cloud-hosted deployments require HMAC-authenticated source URLs, source policy, network safeguards, and workload limits. The raw Gateway origin stays behind the attached Proxy instead of becoming an unrestricted public fetch endpoint.

Which sources are supported?

Built-in policies currently cover Xiaohongshu, Weibo, Pixiv, SSPAI, Instagram, and Piokok, plus generic public HTTP(S) images. Policies are curated by WebP Cloud; additional sources are evaluated from real workloads and may require a scoped update.

What does the Gateway cache?

The Gateway keeps a bounded disk cache of validated original source bytes for origin shielding, request coalescing, and stale recovery. The attached Proxy separately caches transformed delivery variants such as WebP, AVIF, resized, or watermarked output.

Do HMAC-authenticated URLs expire?

The current route contract uses a static HMAC-SHA256 over the decoded original URL and does not include an expiry timestamp. Rotating the deployment secret invalidates previously generated URLs; the attached Proxy and workload limits remain the public access boundary.

How is it billed?

Qualifying Business customers do not pay a separate Gateway add-on fee. Requests still pass through the attached WebP Cloud Proxy and consume the request quota, cache, regions, and support capacity agreed in the Business plan.

Private beta · Business Proxy add-on

Show us the sources your current image pipeline struggles with.

Share a representative URL set, monthly request volume, cache behavior, and delivery topology. We will tell you whether Smart Image Gateway is a fit before proposing a deployment.