Skip to content
Focal
Start free trial
Dashboard

Documentation

Focal sits between your image storage and your users. You keep the originals; Focal produces whatever variant a request asks for and caches it at the edge.

How a request flows

  1. 01

    Your origin

    Any HTTPS location your images are publicly readable at: an S3, GCS or R2 bucket, or your own server. Focal reads from it and never writes back.

  2. 02

    The request

    Your page asks for an image at a size, with a fit mode and any filters, all written in the path.

  3. 03

    The transform

    On a cache miss the engine fetches the source once, applies the operations in order, and encodes the output. This work uses one of your account's workers.

  4. 04

    The cache

    Focal stores the result at the edge and serves later requests from there. A request served from the cache skips the transform and uses no worker.

Your plan sets how many images Focal processes at the same time for your account. See pricing for the worker tiers.

Your first URL

Fixed width, proportional height 
/unsafe/800x0/filters:quality(80)/products/chair.jpg

Read the URL API for the full grammar, including trimming, positioned crops and the filter pipeline.