calendar · fiscal · q1 q2 q3 q4 · live

Find the quarter for any date

Calendar Q1-Q4 by definition (Jan-Mar, Apr-Jun, Jul-Sep, Oct-Dec) plus a configurable fiscal-year start for FY/FQ planning.

Quick Start

Calendar vs fiscal quarters

Calendar quarters are fixed: Q1 = Jan-Mar, Q2 = Apr-Jun, Q3 = Jul-Sep, Q4 = Oct-Dec. Fiscal quarters slide based on when an organisation's fiscal year starts.

  1. 01

    Pick a date

    Any calendar date.

    Parsing accepts ISO 8601, RFC 3339, RFC 2822, and Unix epoch seconds/milliseconds. The Date constructor handles the rest with browser-engine consistency.

    inputISO 8601RFC 3339epochlive
    date · timestampyyyy-mm-dd · ISO
    2026-05-21
    loaded · ISO 8601zone · ready
  2. 02

    Calendar Q

    Month divided by 3, plus 1 — the universal definition.

    All math runs in UTC internally to avoid DST landmines; presentation converts back to the user’s zone via Intl.DateTimeFormat.

    calendarUTC mathIntlDST-safelive
    Q · options1-4 · live
    May → Q2
    options applied · UTCDST-safe
  3. 03

    Pick fiscal start

    January = same as calendar. April, July, October are common in different sectors.

    Output respects the chosen timezone offset (Z vs +05:30) and pads digits per ISO conventions so sorts stay chronological.

    fyoffsetzone-awaresortablepadded
    FY · computedmonth · ready
    FY starts: April
    computed · instantsortable
  4. 04

    Fiscal Q + year

    Same date can be different FY quarters depending on the org.

    Copy writes via the Async Clipboard API; nothing pings a time server — the browser’s clock is the only oracle.

    mapclipboardno oracledeterministicclient-side
    ✓ · copiedready · done
    FY26 Q1
    ready · ready to shipsuccess
Pro tips

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.

Use Cases

When to find a quarter

Reporting, planning, accounting.

Quarterly reports

Know exactly which quarter your data covers. 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-safe

Sales pipeline

Bucket deals by fiscal Q for forecasts. 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-correct

OKR cycles

Quarterly OKRs align to fiscal, not calendar. 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-sortable

Cohort analysis

Group users by signup quarter. 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-grade

Compliance

SEC filings, payroll taxes — all quarterly. 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-aware

Multi-country teams

UK fiscal year starts in April; Japan in April; US fed in October. 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.

i18n
FAQ

Frequently asked questions

An organisation's accounting year. It doesn't have to match the calendar — many countries start in April or October.
FY2026 = April 2025 - March 2026 in this tool's convention. Some orgs use the start year; we use the end year (UK / EU norm).
Convention. Q is unambiguous; bare numbers risk confusion with month or week number.
No — quarters are whole-month buckets. For mid-quarter math, use date-difference.
No — the calculation runs locally in your browser tab.
Suggest a tool

Something missing?

Tell us what you need. We ship the top requests every two weeks.

Sent straight to the maintainers · no account needed
47 in queue·8 shipped this month
Request queued. Thanks!