Purpose and scope
What this timeline establishes
Calculate nominal and skew-adjusted cookie expiration from Max-Age.
The Cookie Expiration Calculator keeps Cookie set time, Max-Age seconds, Clock-skew allowance seconds, and Refresh threshold percent visible beside the result so the inputs can be checked, saved, and reproduced without reconstructing the calculation later.
Instructions
How to use this calculator
Enter the values requested for the Cookie Expiration Calculator and replace every sample with the actual schedule, record, or system being analyzed.
- Use Cookie set time and Max-Age seconds to establish the starting conditions for the Cookie Expiration Calculator.
- Set Clock-skew allowance seconds and Refresh threshold percent to match the actual case rather than leaving example assumptions in place.
- Run the Cookie Expiration Calculator with a baseline set of values, then change only one uncertain input at a time when comparing alternatives.
Calculation
Method used
Max-Age advances from set time, skew creates an earlier effective boundary, and refresh uses the entered fraction.
The displayed formula makes the role of Cookie set time, Max-Age seconds, and Clock-skew allowance seconds explicit. In the Cookie Expiration Calculator, keeping those inputs separate helps distinguish a changed assumption from a changed calculation rule.
Calculation method last reviewed: June 20, 2026.
Worked scenario
Example calculation
To audit your own Cookie Expiration Calculator result, compare Cookie set time and Max-Age seconds with the worked scenario. In the Cookie Expiration Calculator, if the direction or scale looks wrong, verify Refresh threshold percent before changing several inputs at once.
Interpretation
Interpreting the calculated date and buffers
The timeline describes entered lifetime arithmetic and not full browser cookie behavior.
Read the headline together with the supporting metrics for Cookie set time, Max-Age seconds, and Clock-skew allowance seconds. A plausible-looking Cookie Expiration Calculator result can still be unreliable when one of those values uses the wrong unit, date boundary, or local convention.
The Session Idle and Absolute-Timeout Calculator extends the Cookie Expiration Calculator by letting you compare idle expiration with the absolute session lifetime.
Visual audit
Reading the calculated timeline
The Cookie Expiration Calculator timeline orders checkpoints calculated from Cookie set time, Max-Age seconds, Clock-skew allowance seconds, and Refresh threshold percent. When reviewing the Cookie Expiration Calculator, read from the anchor event toward the final boundary and distinguish an operational buffer from the date or time that carries the actual consequence.
Boundaries
Important edge cases and limitations
Browser behavior, Expires precedence, server revocation, SameSite, deletion, and request timing are outside the arithmetic.
If one of these exclusions applies, treat the Cookie Expiration Calculator output as a baseline and correct Refresh threshold percent or another affected input before recalculating.
Practical use
Recommended workflow
Test Max-Age, Expires, deletion, and refresh behavior in the actual browser and server environment.
Use the Access Token Expiry Calculator alongside the Cookie Expiration Calculator to calculate refresh and effective expiration times from issue time, TTL, and clock skew.
Input audit
Checklist for this calculation
- Confirm the source and units for Cookie set time and Max-Age seconds before entering them.
- Preserve Clock-skew allowance seconds and Refresh threshold percent with any saved or shared Cookie Expiration Calculator result.
- For the Cookie Expiration Calculator, review the exclusions above for conditions that could change Refresh threshold percent or the calculation method.
- Recalculate the Cookie Expiration Calculator whenever a recorded input or real-world condition changes.
Questions
Frequently asked questions
Which takes precedence, Max-Age or Expires?
Modern specifications generally give Max-Age precedence, but compatibility and implementation behavior should be tested.
What can make the cookie expiration calculator result misleading?
Browser behavior, Expires precedence, server revocation, SameSite, deletion, and request timing are outside the arithmetic. The timeline describes entered lifetime arithmetic and not full browser cookie behavior.
How is the cookie expiration calculator result calculated?
Max-Age advances from set time, skew creates an earlier effective boundary, and refresh uses the entered fraction. Nominal expiry = set time + Max-Age; effective expiry subtracts skew; refresh uses a selected Max-Age fraction.
Which reference supports the cookie expiration calculator?
The References section links to RFC 6265: HTTP State Management Mechanism for the rule, definition, or method associated with this calculation.
How can the worked example help check the cookie expiration calculator?
A one-hour cookie with thirty seconds of skew receives an effective boundary thirty seconds before nominal expiry. The timeline describes entered lifetime arithmetic and not full browser cookie behavior.
Verification
References
Reference and calculation method reviewed: June 20, 2026.