Return the optimized image immediately.
The first request waits for conversion, then receives the optimized result. This is the quality-first choice for API-style use cases and strict output requirements.
5-minute guide
Your first optimized image, from the origin you already have.
Create one proxy, preserve the image path, and let WebP Cloud handle format negotiation, optimization, caching, and URL-based transforms.
Basic usage
Three steps from origin to edge.
The generated proxy mirrors the path structure of your origin, so integration can begin with a single URL before you update an entire site.
- 01
Create a Proxy
Sign in to the Dashboard with GitHub, choose Create Proxy, and enter the scheme and hostname where your original images are publicly available.
Origin URLhttps://docs.webp.se - 02
Keep the image path
The Dashboard gives the Proxy a WebP Cloud address. Replace only the origin hostname and keep the rest of the image path unchanged.
Proxy URLhttps://559a238.webp.ee - 03
Request and roll out
Open the new URL to create the first optimized result. Test one or two images, then update the hostname in your template, CMS, or application.
Optimized imagehttps://559a238.webp.ee/images/webp-wordpress.png
Readable URL API
Transform the request, not the source file.
Query parameters can resize and tune an image at delivery time. WebP Cloud retains the original path and automatically chooses WebP or AVIF only when the result is smaller.
- Automatic modern-format negotiation and fallback
- Metadata removal reduces size and potential EXIF exposure
- Generated variants are cached after processing
Original image
https://docs.webp.se/images/demo.jpg↓Optimized and resizedhttps://559a238.webp.ee/images/demo.jpg?width=800&quality=80First-request behavior
Choose quality-first or response-first.
Each Proxy can use the behavior that best matches its traffic pattern.
Return quickly, optimize in the background.
The first request receives the origin image after lightweight processing while full optimization runs asynchronously. Later requests receive the cached optimized result.
Quick reference
The parameters most teams start with.
This is a deliberately small subset. The complete documentation covers adaptive resize, watermarks, filters, color adjustments, animated images, and the API.
width, heightResize to exact dimensions; using both dimensions applies attention-aware cropping.
max_width, max_heightCap large images while leaving smaller source images unchanged.
qualityOverride output quality for a request, from 10 through 100.
flip, rotateFlip vertically or horizontally, or rotate the result by an angle.
blur, sharpenApply a blur or sharpen treatment without creating another source file.
meta=fullReturn source metadata including dimensions, size, colorspace, frame count, and BlurHash.
Important limits
Know the source requirements.
- Maximum dimensions
- 16,383 × 16,383 px
- Maximum file size
- 80 MiB
- Origin response
- An image Content-Type or a supported binary Content-Type is required.
Common questions
Before you switch traffic.
Do I need to move or upload my images?
No. WebP Cloud reads from the public image origin you configure. Your source files, CMS, and publishing workflow stay where they are.
What happens after the first request?
The result is cached and subsequent requests are served from cache until a purge or relevant configuration change invalidates it.
Can I keep my own hostname?
Yes. You can start with the generated webp.ee address, then connect a custom domain from the Dashboard.
What happens if quota runs out?
The proxy follows its Operation on Disabled setting: redirect to the origin, deny the request with a 403, or return a placeholder image.
