Delivery

Delivery gives an asset a public address that a website or app can load it from, without signing in. To turn it on, open the asset in the Asset Library, choose Edit, open the Delivery section, turn on Enable delivery and choose Save Changes.

To copy the address, choose Share → Copy delivery link in the asset's ⋯ menu in the Asset Library, or Copy URL for an optimized copy or a 512 px thumbnail of an image. The Delivery section also builds transformed addresses for you.

• New uploads start with delivery on while the project's Deliver new assets by default setting is on under Settings → General, as it is to start. Turn that setting off to make delivery something you turn on asset by asset.
• While delivery is off, or once the asset is in the trash, its addresses return not found.

The asset editor's Delivery section is covered in Asset library.

A delivery address ends in /d/, the project's ID, the asset's ID and the file name. To get a transformed image, add transform steps before the file name, like /d/…/w_800,h_600,c_fill,f_auto,q_auto/hero.jpg.

• w_ and h_: width and height in pixels.
• c_: how the image fits the size: fill, fit, cover, contain, pad, crop or thumb.
• f_: the format: auto, webp, avif, jpg or png.
• q_: quality, auto or 1 to 100.
• e_: an effect: blur, sharpen, grayscale, sepia, negate, brightness, contrast, saturation or tint, with an optional value after a colon, like e_blur:400.

Separate steps with commas, and add another / segment to apply more steps after the first. Transforms work on images, and only when the project's URL transforms setting is on under Settings → General; with it off, Assets serves originals only and refuses transform addresses.

The largest size, the formats and the effects an address can ask for are set in Platform → API → Delivery Settings; by default up to 4000 px a side and 25 megapixels. See Platform and API.

Delivery addresses are public: anyone with the address can load the file, without signing in. Two settings in Platform → API → Delivery Settings narrow that for the whole project.

• Referrer allowlist: only pages on the websites you list can load the files. Left empty, every site can.
• Require signed URLs: every address needs a signature, which you get through the Assets API. Once you save it on, addresses without a valid signature stop working.

Settings in Shared Links don't affect delivery addresses; a shared link is a separate page. See Platform and API and Collaboration.

Delivery → CDN Delivery lists the project's assets with the traffic Assets has logged for each. The figures across the top show CDN storage (the size of assets with CDN switched on, and how many of all assets that is), Requests, Bandwidth and the Cache-hit ratio.

Each row shows the asset's format and size, its requests and bandwidth, and a CDN switch. Filter by All assets, CDN on or CDN off, or search by name and format.

The CDN switch marks an asset as published to the CDN, saves straight away, and starts any workflow with the Asset published trigger. It doesn't decide whether the asset's delivery address works; that's the asset's own Enable delivery setting.

Requests are the times Assets served the project's files, such as previews and downloads. A request counts as a cache hit when the browser already had the current file.

Delivery → Delivery Analytics charts the project's file traffic over Last 7 days, Last 30 days (the default) or Last 90 days.

• Figures: Delivery requests, Bandwidth, Cache hit ratio and CDN coverage (assets with CDN on, out of all assets).
• Charts: bandwidth over time, cache hits and misses each day, top delivered assets, requests by country, transform formats, and CDN coverage.

Export has Export CSV, which saves the numbers behind every chart, and Export PNG, which saves an image of the first chart with data. Until files have been served, the screen shows "No delivery data yet".