How to use Sleep Diary
- Replace the sample Sleep sessions with each session's start/end date, local time and UTC offset. Use the offset that applied at each endpoint, including any clock change.
- Choose Main sleep or Nap, then enter the awakening count and minutes awake within that interval. Only awake minutes are subtracted from elapsed time; the count does not supply a duration.
- Select Review sleep diary. Check In bed and Sleep hours, and correct any overlapping sessions or awake time longer than the interval.
- Read Night as the report-date grouping column: main sessions beginning before 18:00 use the preceding local date; other main sessions use their local start date, and naps always use their local start date. A nap-only group is not another night of main sleep.
- Download sleep-diary.csv for session rows and group columns, or its PDF for the eight session columns. Save sleep-diary.json to restore the original editable records later.
Example: Sleep Diary
The main session lasts 7.5 hours; subtracting 12 awake minutes leaves 7.3 recorded sleep hours. The 25-minute nap belongs to its own start date, giving two report dates for the two sessions.
Options
- Editable fields
- Sleep sessions: Start date, Start time, Start UTC offset, End date, End time, End UTC offset, Session kind, Awakenings, Minutes awake. Add or remove these records with the labeled controls; each new row starts blank.
- Advanced raw input
- Raw input uses five tab-separated cells: two full offset timestamps, main/nap, awakening count and minutes awake. Editable controls split each endpoint into date, time and UTC offset without changing the stored timestamp shape.
- Session grouping
- The evening grouping is a report convention. It does not identify a biological night or select a sleep target.
- Awake minutes
- Only the entered minutes reduce the interval. Awakening count is reported separately; overlapping sessions are refused.
Supported inputs and limits
- Use 1 to 200 sessions and at most 100,000 characters.
- Both endpoints must include real dates, clock times and explicit Z or ±HH:MM offsets.
- End must follow start.
- Overlapping actual instants are refused, while one session may begin exactly when another ends.
- Awakening count is a whole number from 0 to 100 and awake minutes from 0 to 720.
More details
Awake minutes cannot exceed the interval; a positive awakening count also requires positive awake minutes.
Enter a known zero explicitly rather than leaving a required value blank.
Report dates follow the main/nap grouping convention above.
Hours display up to three decimal places.
The CSV includes group main/nap columns; the PDF contains the first eight session columns.
There is no sleep-stage inference, quality score, recommended duration or diagnosis.
Processing is local without automatic saving.
JSON projects from this page are limited to 512 KiB.
Timestamp spellings that native controls cannot represent remain in advanced raw input.
PDF text uses the supported standard-font character set.
Where your input is processed
This tool does not upload your inputs. See the limits for anything saved on your device.
Elapsed time comes from explicit offsets
Start and end timestamps include their UTC offsets. This makes elapsed time independent of the browser location and allows an offset change across daylight-saving transitions. Awake minutes are subtracted from the interval; awakening counts are reported separately. The result is an entered record, not a sleep-quality score or diagnosis.
Questions about Sleep Diary
Does it recommend how long to sleep?
No. It totals the sessions and awake minutes you enter. It does not select a sleep target or judge sleep quality.
What if the clocks changed overnight?
Enter the offset in force at each endpoint. The tool uses the two actual instants and does not guess a time-zone transition.
Can sessions overlap?
Overlapping actual intervals are refused so time cannot be counted twice. A session may start exactly when the previous one ends. Enter the correct offset at each endpoint before comparing their times.