Print-ready monthly & yearly calendar
Pick any year. Switch between a single month or the whole year on one sheet. Print uses the browser dialog with margins suitable for A4 / Letter.
How to print a calendar
Pick year and view, then hit Print. The CSS isolates the calendar area so the rest of the page disappears in the print preview.
- 01
Choose year
Any year — JavaScript Date is happy with very old or very future ones.
Parsing accepts ISO 8601, RFC 3339, RFC 2822, and Unix epoch seconds/milliseconds. The Date constructor handles the rest with browser-engine consistency.
yearISO 8601RFC 3339epochliveyear · timestampinput · ISO2026
loaded · ISO 8601zone · ready - 02
Pick view
Single month for the fridge, whole year for a wall planner.
All math runs in UTC internally to avoid DST landmines; presentation converts back to the user’s zone via
Intl.DateTimeFormat.viewUTC mathIntlDST-safeliveview · optionsyear · live12 mini-grids
options applied · UTCDST-safe - 03
Print
Browser dialog handles A4 / Letter / PDF.
Output respects the chosen timezone offset (
Zvs+05:30) and pads digits per ISO conventions so sorts stay chronological.printoffsetzone-awaresortablepaddedprint · computeddialog · readyA4 portrait
computed · instantsortable - 04
Hang it up
Clean grayscale design — no ink-hungry colour.
Copy writes via the Async Clipboard API; nothing pings a time server — the browser’s clock is the only oracle.
useclipboardno oracledeterministicclient-side✓ · copiedready · done✓ Printed
shipped · ready to shipsuccess
Time math without DST landmines
Always store UTC
Convert to local for display only. UTC storage avoids DST jumps and timezone drift in databases.
Watch leap seconds
POSIX time doesn’t count leap seconds; some systems do. Don’t use timestamps for sub-second precision across boundaries.
Prefer Temporal eventually
The Date API has many quirks. Temporal is shipping in modern engines and handles zones correctly.
Cron is timezone-tricky
Cron expressions run in the daemon’s local zone unless told otherwise. Pin a TZ explicitly for predictable runs.
ISO 8601 sorts naturally
YYYY-MM-DDTHH:mm:ss sorts correctly as a string. Don’t use US-style MM/DD/YYYY for anything machine-readable.
Beware Y2K38
Signed 32-bit Unix timestamps overflow in 2038. Use 64-bit storage end-to-end for long-lived systems.
When to print a calendar
Home, office, planning.
Wall planner
Year on one page for the office wall. Math runs in UTC under the hood to dodge DST jumps — local time is only for display. That means scheduling logic and date diffs survive March / November fall-back without the classic off-by-one-hour bug.
DST-safeSprint planning
Print a month with sprint boundaries marked. Browser clock is the only source — no external time server, no privacy leak, no rate limit. Pair with NTP-synced server time for high-accuracy use cases, but for human-scale work the browser clock is plenty.
UTC-correctFamily schedule
Stick a month on the fridge. ISO 8601 output sorts naturally as strings, perfect for filenames (report-2026-01-15.pdf) and log lines that need chronological ordering without parsing. Drop into S3 keys for free time-bucketing.
ISO-sortableTeaching
Hand out blank calendars for date exercises. Pairs cleanly with cron, scheduled tasks, and timestamped log analysis. The tool's output drops directly into APScheduler, Linux cron, or GitHub Actions schedule expressions without re-formatting.
spec-gradeProduction schedule
Print a shoot or release schedule. Output respects the chosen timezone offset (Z vs +05:30) so REST APIs and database TIMESTAMP WITH TIME ZONE columns round-trip cleanly. No ambiguity between "noon UTC" and "noon local".
zone-awareTravel planning
Mark itinerary days by hand. Confirms the difference between epoch seconds (10 digits) and milliseconds (13 digits) before you commit code that mis-multiplies by 1000 — a classic bug in cross-language time handling.
epoch-accurateFrequently asked questions
Something missing?
Tell us what you need. We ship the top requests every two weeks.