导航|地址|刷新
Edge and Browser Cache TTL

Skip to contentDocumentation Index
Fetch the complete documentation index at: https://developers.cloudflare.com/cache/llms.txt
Use this file to discover all available pages before exploring further.



DocsDirectoryAPISDKsChangelog

Search

Log in






Cache / CDN

/




Overview

Plans

Get started


Concepts


CDN-Cache-Control

Cloudflare cache responses

Customize cache

Default cache behavior

Head Requests and Set-Cookie Headers

Origin Cache Control

Retention vs Freshness (TTL)

Revalidation

Vary






Cache configuration



Purge cache


Overview

Purge by single-file

​Purge everything

Purge cache by cache-tags

​Purge cache by hostname

​Purge cache by prefix (URL)

Purge cache key resources

P​urge varied images

Purge zone versions via API






Cache Response Rules


Overview

Create a rule in the dashboard

Create a rule via API

Terraform example

Available settings






Cache Rules


Overview

Create a rule in the dashboard

Create a rule via API

Terraform example

Available settings

Order and priority


Examples


Overview

Browser Cache TTL

Bypass Cache on Cookie

Cache by Device Type

Cache Deception Armor

Cache everything for hostnames in a list

Cache Everything while ignoring query strings

Cache Level (Cache Everything)

Cache TTL by status code

Custom Cache Key

Edge Cache TTL

Origin Cache Control

Query String Sort

Respect Strong ETags





Migration from Page Rules






Edge and Browser Cache TTL


Overview

Set Browser Cache TTL





Always Online

Cache by status code

Cache keys

Caching levels

Tiered Cache






Advanced configuration


Serving tailored content

Cache Reserve

Crawler Hints

Early Hints

Query String Sort

Vary for images






Performance review


Cache Analytics

Cache performance






Cache security


Avoid web cache poisoning

Cache Deception Armor

Cross-Origin Resource Sharing (CORS)






Reference


CDN Reference Architecture ↗

CSAM Scanning Tool

Development Mode

Using ETag Headers with Cloudflare






Interaction with Cloudflare products


Customize cache behavior with Workers

How Workers interact with Cache Rules

Enable cache in an R2 bucket

Control cache access with WAF and Snippets






Troubleshooting


Dynamic content and login issues

Issues with MP4 videos on iOS and Safari

Bot Management cookie causes cache bypass in O2O setups

edgeResponseBytes and cacheResponseBytes discrepancy

Always Online





Changelog

Glossary


Agent resources


Agent setup ↗

Cloudflare Skills ↗

Code Mode MCP Server ↗

Domain-specific MCP Servers ↗MCP

Cache llms.txt ↗

Cache llms-full.txt ↗

Cloudflare Docs llms.txt ↗

Cloudflare Docs llms-full.txt ↗













Home

/Cache / CDN

/Cache configuration

/Edge and Browser Cache TTL



Edge and Browser Cache TTL


Last updated Apr 16, 2026|Copy as Markdown|View as Markdown|Agent setup

OverviewEdge Cache TTLBrowser Cache TTL





Edge Cache TTL


Edge Cache TTL (Time to Live) specifies the maximum time to cache a resource in the Cloudflare global network. Edge Cache TTL is not visible in response headers and the minimum Edge Cache TTL depends on plan type.

	Free	Pro	Business	Enterprise
Availability	Yes	Yes	Yes	Yes
Minimum Edge Cache TTL	2 hours	1 hour	1 second	1 second

For more information on how to set up Edge Cache TTL, refer to Cache rules.


Browser Cache TTL


The Browser Cache TTL sets the expiration for resources cached in a visitor’s browser. By default, Cloudflare honors the cache expiration set in your Expires and Cache-Control headers but overrides those headers if:

The value of the Expires or Cache-Control header from the origin web server is less than the Browser Cache TTL Cloudflare setting.

The origin web server does not send a Cache-Control or an Expires header.

Unless specifically set in a cache rule, Cloudflare does not override or insert Cache-Control headers if you set Browser Cache TTL to Respect Existing Headers.


Note


Setting high Browser Cache TTL values means that the assets will be cached for a long time by users’ browsers.

If you modify cached assets, the new assets may not be displayed to repeat visitors before the Browser Cache TTL expires.

Purging Cloudflare’s cache does not affect assets stored by a visitor’s browser.

	Free	Pro	Business	Enterprise
Availability	Yes	Yes	Yes	Yes
Minimum Browser Cache TTL (Page Rules)	2 minutes	2 minutes	2 minutes	30 seconds
Minimum Browser Cache TTL	1 second	1 second	1 second	1 second
Default Browser Cache TTL	4 hours	4 hours	4 hours	4 hours

For more information on setting the Browser Cache TTL, refer to Set Browser Cache TTL.


PreviousMigration from Page RulesNextSet Browser Cache TTL


Was this helpful?

YesNo

Edit pageReport issue




On this page

Overview

Edge Cache TTL

Browser Cache TTL


Edit pageReport issue














Getting started
PlansContact salesPartnersFind a partnerStartupsUnder attack?Domain name search


Company
AboutCareersInvestorsPressPress kitGlobal network




Public interest
Project GalileoAthenian ProjectCloudflare for CampaignsProject FairshotImpact/ESG


Compliance
Compliance resourcesTrust HubData ProtectionResponsible AITransparency reportReport abuse




Resources
App innovation reportCloudflare RadarCase studiesStatusSupportEventsBlog


Developers
DocumentationLearning centerCommunity




Solutions
SSE and SASE platformCloudflare AI CloudAI SecurityFrontend Development PlatformMulti-Tenant Platform DevelopmentWeb Security Platform


Start BuildingLog In












© 2026 Cloudflare, Inc.

Privacy policy|Report security issues|Terms of use|Trademark
|
Your privacy choices








Docs




------
导航页 打开网址