01
Choose your CSV
Choose one UTF-8, comma-separated calendar CSV up to 1 MB from your device.
Validate calendar rows and download a Google Calendar-ready CSV or one-time ICS file without guessing dates.
Use a comma-separated UTF-8 file up to 1 MB. Google Calendar requires English headers and comma-separated fields.
Your CSV stays in your browser. It is not uploaded to our servers.
Data handling
Advertising and analytics are separate site services. We do not send selected tool input to them. Read the Privacy Policy for details.
How it works
01
Choose one UTF-8, comma-separated calendar CSV up to 1 MB from your device.
02
Choose the columns and one date format for the whole file, then review every exception by source row.
03
Download valid events as Google Calendar CSV or one-time-event ICS.
Example
If your source uses 17/06/2026, choose DD/MM/YYYY once. The export writes the Google-ready date as 06/17/2026, without guessing a different interpretation for another row.
Every ready event has a Subject and Start Date. Timed events also need a valid Start Time.
A repeated title and start date is flagged with the earlier source row before import.
The download uses Subject, Start Date, Start Time, End Date, End Time, All Day Event, Description, Location, and Private.
The CSV is parsed and generated in the browser, without uploading your events.
Questions
Subject and Start Date are required by Google Calendar. This tool requires a Start Time only when the event is not marked all-day.
Dates such as 06/07/2026 can mean June 7 or July 6. One explicit choice keeps every source row consistent instead of silently guessing.
Google Calendar documents a 1 MB maximum for imported CSV and iCalendar files. The tool applies the same limit so a ready download remains within Google’s stated file-size limit.
Yes. It creates one VEVENT for each ready source row and preserves the local clock time without guessing a timezone. Recurring events and timezone definitions stay outside this version’s scope.
Yes. Commas, semicolons, backslashes, and line breaks in event titles, descriptions, and locations use the RFC 5545 text escaping rules.
No. The CSV is read, checked, and generated locally in your browser. Got A Tool does not receive or store its contents.
Practical guide
Review timezones, recurring events, and the receiving calendar's preview before you import or share a working copy.
Open the guide →Keep working
Convert calendar events to CSV without shifting original event times.
Open tool →Split CSV files by size or row count. Keep related rows together, repeat headers and download every part as a ZIP — privately in your browser.
Open tool →Convert CSV to JSON or JSON objects to CSV locally with validation and spreadsheet-safe output.
Open tool →Create campaign URLs from a CSV, report invalid rows, and download only valid links.
Open tool →