Find MyWay TripExplore holidays

How to export public holidays to CSV

Download holiday dates for spreadsheets, planning, and analytics.

Share

FacebookXWhatsAppTelegramLinkedIn

Overview

CSV exports are ideal when you want to work with holiday data instead of just viewing it.

Use CSV when you want to:

  • plan staffing and coverage
  • build a holiday policy list
  • model the impact of long weekends on lead times
  • create pivot tables (holidays by month, by quarter)
  • combine multiple countries into one spreadsheet

On this site, CSV exports are generated from the country-year (or region-year) calendar you’re viewing.

Step 1 — Pick the country/region and year

Start from a country page (or region page if relevant), then choose the year.

Examples:

  • /public-holidays/united-kingdom
  • /public-holidays/australia
  • /public-holidays/canada

Tip: if you’re planning a project that spans the end of a year, export two years and combine them in a spreadsheet.

Step 2 — Download the CSV

On the calendar page, click Download CSV.

You’ll get a .csv file that you can open in Excel, Google Sheets, Numbers, or import into analytics tools.

Step 3 — Import into Excel (recommended approach)

Opening a CSV by double-click can sometimes cause formatting issues (especially with dates). A safer method is to import.

General tips:

  • Confirm the delimiter is comma.
  • Confirm the date column is recognised as a date.
  • If you see dates turning into unexpected formats, set the date column explicitly.

Step 4 — Import into Google Sheets

Google Sheets is usually forgiving with CSV files.

Best practice:

  • Import the CSV into a dedicated sheet tab named like “Holidays — [Country] — [Year]”.
  • Freeze the header row.
  • Add columns for “Team/location impacted” or “Office closed?” if you need internal operational metadata.

What you can do with holiday CSV data

Build a quarter-by-quarter view

Create a pivot table:

  • Rows: Month or Quarter
  • Values: Count of holidays

This quickly shows “holiday-heavy” periods.

Identify long-weekend patterns

Add a computed column:

  • Day of week for each holiday

Then filter for Monday/Friday holidays to see long-weekend frequency.

Combine multiple countries

If you support an international team:

  1. Export CSV for each country.
  2. Combine into one sheet.
  3. Add a “Country” column.
  4. Use filters to view impacts by team.

This is much easier than trying to keep a single mega-calendar in a calendar app.

CSV columns explained (this site’s export)

The CSV export from this site includes these columns:

  • Date: the holiday date in ISO format (YYYY-MM-DD)
  • Name: English/common holiday name
  • LocalName: local language name when available
  • Type: holiday type (public, bank, school, etc. depending on the dataset)
  • ObservedDate: observed/substitute date when applicable
  • Status: data status (for example, confirmed vs estimated when the dataset supports it)

Tip: If you’re building an internal holiday policy list, keep both Date and ObservedDate. The observed date is often what matters for operational closures.

Useful spreadsheet patterns

1) Create a “working day impact” column

Add a computed column:

  • Does the holiday fall on a weekday?
  • Is the observed date a weekday?

This helps you estimate real operational impact.

2) Build a “holiday season” window

Many teams treat late December and early January as one season. In a spreadsheet, you can filter for dates between (for example) Dec 15 and Jan 15 across years.

Add columns like:

  • Office closed? (Yes/No)
  • Reduced coverage? (Yes/No)
  • On-call required? (Yes/No)

This turns a holiday list into an operational plan.

Data hygiene tips

  • Keep raw exports in one tab (“Raw — 2026”).
  • Do transformations in another tab (“Analysis”).
  • Document any manual edits so you can reproduce them next year.

Advanced: Power Query / data pipelines

If you use Excel Power Query, Power BI, or other ETL tools, CSV exports are a convenient input.

Suggested approach:

  1. Store each CSV export in a dedicated folder (by year).
  2. Load them via Power Query as a combined table.
  3. Add calculated fields (month, quarter, weekday).
  4. Build dashboards: holiday counts by location, holiday-heavy weeks, etc.

This approach is particularly valuable for operations teams that need repeatable reporting.

Helpful formulas

Here are a few generic formulas/patterns you can use in spreadsheets:

  • Weekday: compute weekday from Date to see long-weekend potential.
  • Month: extract month for grouping.
  • IsObservedDifferent: check if ObservedDate differs from Date.

Once you have these, you can filter to “ObservedDate is not blank” to focus on holidays with substitute/observed behavior.

Worked example: turning a CSV into a planning sheet

Here’s a simple workflow that works well for most teams:

  1. Import the CSV for your country/year.
  2. Add a column “OperationalDate”:
  • If ObservedDate is present, use ObservedDate.
  • Otherwise use Date.
  1. Add a “Weekday” column from OperationalDate.
  2. Add an “Impact” column (High/Medium/Low) based on your organisation’s reality.

This creates a practical sheet you can use for scheduling and staffing without losing the original holiday dates.

Reading “Status” and “Type” safely

The CSV includes both Type and Status to help you interpret what you’re seeing.

Type

Type usually indicates what kind of holiday it is in the dataset (for example: public, bank, school, optional). Do not assume that “public” means every employer is closed. Treat Type as a signal, then confirm impact for your context.

Status

Status can indicate whether the date is confirmed or still estimated in the underlying dataset. In practice, the holidays most likely to be estimated are those tied to lunar calendars or those that depend on announcements.

If your planning is high-impact, use Status as a prompt to cross-check with official sources.

Building a multi-country master sheet (repeatable)

If you manage an international team, a repeatable spreadsheet design saves time year after year.

Suggested columns:

  • Country
  • Region (optional)
  • OperationalDate (ObservedDate if present, else Date)
  • Name
  • LocalName
  • Type
  • Status
  • Team impacted (your internal tag)
  • Coverage plan (your internal note)

With this structure, you can filter quickly and generate “coverage calendars” for each department.

Joining holiday data with your own data

CSV exports become especially valuable when you combine them with your internal datasets.

Common joins:

  • Team roster by location → map “Country/Region” to people who are likely to be offline.
  • Support schedules → mark coverage risk days.
  • Shipping lead times → model delays around long weekends.

Even a simple join (team → country) lets you answer practical questions like: “How many of our on-call engineers are likely affected next Monday?”

Turning CSV into a simple coverage calendar

If you want something managers can use quickly:

  1. Keep OperationalDate, Name, Country, and Impact columns.
  2. Add a “Coverage needed?” column.
  3. Filter to Impact = High.
  4. Share as a read-only sheet.

This gives you a lightweight “holiday risk calendar” without needing a full BI stack.

A template you can reuse every year

To reduce annual work:

  • Keep a spreadsheet template with formulas and pivot tables already set up.
  • Each year, import the new CSV into the Raw tab.
  • Refresh pivots/charts.

This is faster and more consistent than building a new spreadsheet each year.

One-minute checklist

Before you publish or rely on a holiday spreadsheet:

  • Confirm you exported the correct country/region and year.
  • Confirm Date and ObservedDate are interpreted as dates (not text).
  • Decide whether your operations will use Date or ObservedDate as the primary “closure” date.
  • Filter for Status values that imply uncertainty and cross-check critical ones.

Closing note

CSV is most powerful when you treat it as an input to a repeatable process. If you build a small template once, next year’s update becomes a two-minute refresh instead of a full rebuild.

CSV format reference

Create “blackout dates” for scheduling

Many teams define internal “avoid scheduling” days:

  • major public holidays
  • local holidays affecting key offices
  • the day after major holidays (for travel recovery)

CSV is a great starting point: add your internal policy columns and publish a clean policy sheet.

Common issues and fixes

“The CSV shows dates as text”

Fix by converting the date column:

  • In Excel: use Text to Columns or set the column type to Date.
  • In Sheets: use DATEVALUE if needed.

“I need the observed date, not the historical date”

Observed/substitute rules vary by country. Use the calendar page to confirm how dates are listed and whether observed/substitute days are included.

“I need regional holidays”

If the country has region data, export from the regional calendar page rather than the national page.

When ICS is a better choice

If your goal is “make sure nobody schedules meetings on holidays,” ICS is usually the better option because it shows up directly in calendars.

If your goal is “model impact and produce reports,” CSV is better.

Explore country calendars

If “How to export public holidays to CSV” affects schedules or planning, use a small set of country pages as a quick cross-check before you generalize.

  • United States — a common reference point for “How to export public holidays to CSV”.
  • United Kingdom — a common reference point for “How to export public holidays to CSV” in Europe-focused contexts.
  • Canada — a practical reference for “How to export public holidays to CSV” in North America.
  • Australia — a practical reference for “How to export public holidays to CSV” in Oceania.
  • India — a practical reference for “How to export public holidays to CSV” in South Asia.

You can then browse /public-holidays for a broader set of countries relevant to “How to export public holidays to CSV”.

Sources

Related guides

Holiday policies for remote teamsHow to export public holidays to ICS