Web browser cookie capacity
Web browser cookie capacity is the minimum amount of data a browser must reliably store for each HTTP cookie, including its name, value and attributes.
Also known as: browser cookie size, HTTP cookie capacity
How big is it?
4.096 kB of data
Minimum per-cookie capacity · standard minimum
A little perspective
About 1.37 times the data of Text page.
Text page: A digital file containing one page of plain text characters without formatting or embedded fonts.
Measurements, assumptions & sources +
Web browser cookie capacity
RFC 6265 says general-purpose user agents should support at least 4,096 bytes per cookie, counting name, value and attributes. This is an interoperability minimum, not a universal hard browser limit.
RFC 6265 — HTTP State Management Mechanism
The marked minimum per-cookie capacity is calibrated. Unmeasured illustration details are representative.
Text page
A defined 3,000-byte UTF-8 text page using single-byte characters; formatting and embedded fonts excluded.
Defined examples — our methodology
The marked data is calibrated. Unmeasured illustration details are representative.
Change your perspective
Put it next to…
Choose a suggestion to redraw the comparison, or open its page to learn what it is.
Why this measurement?
Why we use 4.096 kB
For comparison, this page uses minimum per-cookie capacity. The record labels the measurement standard minimum; that status is retained wherever the value is compared.
RFC 6265 says general-purpose user agents should support at least 4,096 bytes per cookie, counting name, value and attributes. This is an interoperability minimum, not a universal hard browser limit.
The identifying illustration and the numerical comparison remain separate. How calibrated comparisons work →
Recorded properties
Web browser cookie capacity dimensions and measurements
| Property | Selected value | Recorded range | Basis |
|---|---|---|---|
| 4.096 kB | Not recorded | standard minimum |
Around this scale
Go smaller. Go bigger.
These links use compatible data records, ordered around the selected value.
Sources and method
Want to check the number?
The source records and measurement method remain available for inspection.
- RFC 6265 — HTTP State Management MechanismGeneral-purpose user agents should support at least 4,096 bytes per cookie, including name, value and attributes.
There’s always another scale


