iCalendar to JSON

Online iCalendar to JSON Converter

Turn ICS/iCalendar into JSON from mapped event properties—text, file upload, or Load Sample. Quick conversion with copy or download.

Map structured fields from iCalendar into a dependable JSON result for repeatable data workflows.

Conversion focus

Private by design: iCalendar content is processed locally in the browser.

Need Custom Conversion?

ConversionTab date / time standard (ICS → table)

Calendar fields such as DTSTART, DTEND, DTSTAMP, CREATED, and LAST-MODIFIED are exported as ISO-like text (not raw Excel serials): for example 1997-07-14T17:00:00Z for UTC, 1997-07-14T17:00:00+05:30 for a fixed offset, 1997-07-14 for all-day style dates, or 1997-07-14T17:00:00 when the ICS value has no Z / zone. EXDATE / RDATE lists use commas between values in the same style.

If you edit the file elsewhere and later convert back to ICS (e.g. from Excel), use these same shapes in cells—or real Excel Date/Time cells—so start/end and timestamps map reliably. Locale-only strings (e.g. 14/07/1997 alone) are not guaranteed to parse.

ICS file

Drop a file here, or click to browse

Max 25 MB. Loads into the same editor as the Text tab; use Convert below.

Each row is an iCalendar property found in your VEVENT data. Edit Mapping to set the column title in the exported json output; use Include to omit properties.

# ICS value Mapping Include
Provide valid iCalendar above to load output options.

Map each VCF field to a normalized table column. Use Include to choose output lines; Check all / Uncheck all sit under the mapping table.

# VCF Field Mapping Include
Provide input above to load mapping options.
Include column:

Column names and types feed SQL generation (same rules as the CSV tool).

# Field Name Data Type Max Size Key Include Trim NULL empty
Provide input to load columns.

What this conversion is for

Built for cases where iCalendar is the authoring truth and JSON is the runtime or publish surface. You get arrays/objects that match what HTTP APIs and test harnesses expect.

Use this output next

JSON → XML

Legacy services and XSD pipelines.

JSON → YAML

Config repos and CI matrices.

JSON → CSV

Sheets, Git diffs, and warehouse CSV.

JSON → HTML

Web display and CMS embeds.

From iCalendar to JSON in four moves

Paste iCalendar text or upload the calendar/contact file.

Scan VEVENT blocks, DTSTART/DTEND, and UID lines for obvious duplicates.

Use mapping or options on this page so each iCalendar field lands in the correct JSON shape.

Convert to JSON text for APIs, fixtures, or browser consumers.

Before you convert

  • Recurrence (RRULE) and timezone rules may simplify when flattened.
  • JSON output should be treated as a snapshot until the next source refresh.
  • Keep a copy of the original iCalendar as the audit trail after you ship JSON.

Choose the right output

When JSON is the right output

  • You are promoting iCalendar into JSON because the next hop names that format in its contract or runbook.
  • Downstream asked explicitly for JSON while editors still live in iCalendar.
  • You need a deterministic export for CI, legal, or partner review—not a live sync.
  • The receiving system has a documented JSON ingest path (template, parser, or app import).

When another format fits better

  • Humans must edit in a grid—XLSX or CSV is kinder than raw JSON for reviews.
  • You need printable sign-off—PDF beats JSON for boards and invoices.
  • Calendar/contact semantics belong in ICS/VCF, not JSON wrappers alone.
  • Huge documents should be streamed or paginated—avoid giant single JSON blobs in email.

Continue with other formats

ICS → HTML

CMS and static web tables instead of JSON.

ICS → CSV

Flat pipelines and spreadsheet handoffs instead of JSON.

ICS → XML

Schema-heavy integrations instead of JSON.

ICS → PDF

Print-ready snapshots instead of JSON.

ICS → XLSX

Typed spreadsheet review instead of JSON.

Suggested workflow
  1. Paste iCalendar content or upload a compatible file.
  2. Review detected columns, mappings, and optional limits before conversion.
  3. Convert to JSON, preview when the page supports it, then download the result.

Reviewed iCalendar → JSON notes

Overview, mapping, pitfalls, and FAQs from the same bundle as other ConversionTab converters—open the sections you need.

iCalendar to JSON overview

iCalendar to JSON Converter Overview

Easily convert iCalendar files into JSON with the iCalendar to JSON Converter, ideal for JSON files.

Designed for modern APIs, it offers secure and accurate conversions, making developer workflows transformations effortless.

Provide iCalendar data via text input or file upload, or use Load Sample for the sample event. Map columns, pick JSON as the output format, and you’ll receive your converted file quickly.

Once the JSON output is ready, you can copy it using the copy icon or save it as a file by specifying a file name.

Input format notes

About iCalendar as the source

iCalendar is parsed as structured input for this page. Use complete rows, valid syntax, and consistent field names so the converter can preserve the important data when creating JSON.

Output format notes

About JSON as the output

JSON is generated from the parsed iCalendar data. Review the output before importing it into another system, especially when the destination expects strict columns, dates, or contact fields.

Conversion guide

How to Convert ICS to JSON?

Step 1: Input iCalendar Data:

Provide your ICS text on the Text tab or upload a file on the File tab via 'Drop/Browse File'. Click Load Sample to load the sample calendar.

Step 2: Mapping Columns:

Open the mapping section and align iCalendar property names to the column labels you want in the JSON-oriented table.

Step 3: Include Desired Properties:

Use Include checkboxes to choose which properties appear as columns before conversion.

Step 4: Proceed with Conversion:

When mapping looks correct, click Convert to build JSON from the selected columns.

Step 5: Copy or Download JSON:

The JSON appears in the output area; copy it to the clipboard or use Download to save a .json file (you can set the file name when prompted).

Step 6: Date / time standard:

Calendar fields export as fixed ISO-like text (for example 1997-07-14T17:00:00Z for UTC, 1997-07-14 for date-only, or with ±HH:MM when the ICS used an offset). EXDATE / RDATE use comma-separated tokens in the same style. There is no per-column custom format picker—reuse this shape when preparing data for a round-trip back to ICS.

Questions before converting

ICS (iCalendar) to JSON Conversion FAQs

1. What is iCalendar (ICS) to JSON conversion on ConversionTab?

iCalendar (ICS) to JSON conversion on ConversionTab allows you to convert iCalendar files or iCalendar text strings into JSON (JavaScript Object Notation) format.

2. How do I provide my iCalendar data for conversion?

You can input your iCalendar data in two ways:

  • Text: Users can manually input ICS data as a valid string in this tab.
  • File Tab: Users can upload their ICS file through the 'Drop/Browse File' feature, simplifying the process of working with existing data.

3. Which iCalendar versions are supported for conversion?

ConversionTab supports a range of iCalendar versions, including iCalendar 2.0, for conversion.

4. How do I initiate the conversion process?

After entering your iCalendar data or selecting a file, click the 'Convert' button to start the conversion process.

5. What happens if my provided data is not a valid iCalendar file or string?

If your input data is not a valid iCalendar file or string, ConversionTab will display an error message, and the conversion will not proceed.

6. Can I customize the JSON output format?

ConversionTab currently provides JSON output using a default format. Customization of JSON output format is not available at this time.

7. Is there an option to preview the JSON output before conversion?

Yes, you can preview a sample of the JSON output to ensure that the conversion results meet your expectations before proceeding with the conversion.

8. How do I obtain the JSON output?

Once mapping and settings are finalized, users can initiate the conversion process by clicking the 'Convert' button. The resulting JSON data is displayed in a textarea, providing users with two options:

  • Copy: Users can copy the generated JSON data for immediate use.
  • Download: Users can download the JSON file, with the option to specify a custom file name if desired.

This flexibility ensures seamless access to converted data in the preferred format.

9. Is there sample iCalendar data, and how do I clear the editor?

ConversionTab offers additional features to improve the user experience:

  • Load Sample: Click Load Sample to load the sample calendar (Project XYZ meeting with EXDATE, RDATE, GEO, and more).
  • Clear: Use Clear to reset input and output when you want a clean slate.

10. How can I clear the output and start over?

Click Clear to clear the output and start again.

Explore more conversions

Same goal, other inputs

VCF → JSON

VCF as authoring when APIs expect JSON payloads.

XML → JSON

XML as authoring when APIs expect JSON payloads.

YAML → JSON

YAML as authoring when APIs expect JSON payloads.

CSV & workbook bridges

CSV → JSON

Spreadsheet-first path to the same shape.

XML → CSV

Tree to grid for review.

XLSX → CSV

Workbook to pipeline text.