Overview
Use it when the format needs to change, not the meaning
Use this guide when you already have a seconds value and need a readable duration for notes, configs, or handoffs.
TTL planning
Map caching or DNS TTLs to human-friendly durations for incident notes and runbooks.
SLA calculators
Flip uptime commitments into readable durations for alerts, budgets, and scripts.
Supported inputs
Bring clean source text and keep the direction straight
- Seconds input accepts positive integers and treats blank preset fields as zero.
- The largest values stay usable for long retention windows and future schedules.
- Use the quick presets when you want common TTL starting points before editing the final number.
Walk through it
Follow the same sequence you see in the tool
Workflow
Convert seconds into a readable duration
Use the main form when you already know the raw seconds value and want the TTL breakdown.
- Paste the seconds value or choose a preset that matches your use case.
- Submit the value to generate days, hours, minutes, and seconds plus any localized helper text.
- Review the formatted breakdown before you copy it into notes, configs, or an incident thread.
- Copy the readable summary or the raw seconds value for the next step in your workflow.
What you get
Check the result before you copy it into the next step
Readable duration
The main result restates the seconds value in days, hours, minutes, and seconds so people can read it quickly.
Preset context
Preset cards show when to use each TTL so you can keep the number tied to its real-world purpose.
Copy-ready values
Use the copy controls to move the formatted breakdown or the original seconds value into the next tool.
Avoid these mistakes
Small input problems create the biggest conversion errors
Assuming the preset is enough
Treat presets as a starting point. Adjust the final seconds value before you share the result anywhere important.
Skipping the breakdown check
Verify the rendered duration before you copy it, especially for long TTLs or retention windows.