Technical and media time

Cookie Expiration Calculator

Calculate nominal and skew-adjusted cookie expiration from Max-Age.

PrivacyRuns in your browser
OutputDeadline timeline
CostFree to use
Deadline timeline

Enter your details

Adjust the planning assumptions below.

Calculations stay in this browser. Saved inputs and recent results use local browser storage until you clear them.

Your schedule will appear here

Results update after calculation and include a visual timeline, calendar, or dashboard.

Purpose and scope

What this timeline establishes

Calculate nominal and skew-adjusted cookie expiration from Max-Age.

The Cookie Expiration Calculator creates checkpoints from Cookie set time, Max-Age seconds, Clock-skew allowance seconds, and Refresh threshold percent; Save Refresh threshold percent separate from internal buffers.

CategoryTechnical and media time
Review focusDeadlines and buffers
OutputCalculated checkpoints

Instructions

How to use this calculator

Confirm Cookie set time and Max-Age seconds as the Cookie Expiration Calculator control point, then save Clock-skew allowance seconds and Refresh threshold percent tied to the applicable reference data.

  1. Confirm Cookie set time and Max-Age seconds as the controlling Cookie Expiration Calculator constraint.
  2. Confirm Clock-skew allowance seconds and Refresh threshold percent from the applicable reference data.
  3. Create the Cookie Expiration Calculator checkpoints, then trace Refresh threshold percent in chronological order.
  4. Evaluate the Cookie Expiration Calculator reference with the Refresh threshold percent definition or convention.

Calculation

Method used

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.

The Cookie Expiration Calculator applies Cookie set time, Max-Age seconds, and Clock-skew allowance seconds in sequence; trace the Refresh threshold percent allowance at each checkpoint.

Calculation method last reviewed: June 21, 2026.

Visual audit

Reading the calculated timeline

The Cookie Expiration Calculator timeline creates checkpoints from Cookie set time, Max-Age seconds, Clock-skew allowance seconds, and Refresh threshold percent. Trace Refresh threshold percent from the anchor toward the constraint carrying the consequence.

Interpretation

Interpreting the calculated date and buffers

The timeline describes entered lifetime arithmetic and not full browser cookie behavior.

Trace the Cookie Expiration Calculator deadline separately from Refresh threshold percent; internal buffers remain adjustable unless the reference data fixes them.

Worked scenario

Example calculation

Example: A one-hour cookie with thirty seconds of skew receives an effective boundary thirty seconds before nominal expiry.

Evaluate the Cookie Expiration Calculator control event with Cookie set time and Max-Age seconds, then trace each Refresh threshold percent adjustment.

Boundaries

Important edge cases and limitations

Browser behavior, Expires precedence, server revocation, SameSite, deletion, and request timing are outside the arithmetic.

Replace the Cookie Expiration Calculator allowance when Refresh threshold percent differs from the reference data rule; create its dependent checkpoints again.

Practical use

Recommended workflow

Test Max-Age, Expires, deletion, and refresh behavior in the actual browser and server environment.

Input audit

Checklist for this calculation

  • Trace the Cookie Expiration Calculator control point in Cookie set time and Max-Age seconds.
  • Save Refresh threshold percent separate from discretionary buffers.
  • Evaluate the earliest Cookie Expiration Calculator checkpoint with its constraint.
  • Evaluate the Cookie Expiration Calculator reference with the Refresh threshold percent date and use case.

Verification

References

Reference and calculation method reviewed: June 21, 2026.

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.

When should RFC 6265: HTTP State Management Mechanism be checked for the

Evaluate RFC 6265: HTTP State Management Mechanism with Refresh threshold percent whenever the Cookie Expiration Calculator constraint affects a decision. Save its version or access date beside Cookie set time.

Which convention should Cookie set time use in the

Cookie set time supplies the controlling Cookie Expiration Calculator boundary; Refresh threshold percent changes a dependent checkpoint or allowance. Trace that Refresh threshold percent allowance before moving the constraint.

What changes when Refresh threshold percent is adjusted in the

Create the Cookie Expiration Calculator with a second Refresh threshold percent value, then evaluate checkpoints from Cookie set time outward. The changed Refresh threshold percent identifies the allowance moving the constraint.