Studio review
2026-11-16 09:30:00 – 2026-11-16 10:00:00
UTC+01:00
Meeting room 2
Repeats every week on Monday; 4 occurrences total.
Event details
Review the sketches and agree on next steps.
Convert an older VCS calendar to ICS. Upload or paste your file, check the events, and download it for your calendar app. Free, with no account needed.
Drop a .vcs file here
or choose one from your device.
Example source: example-calendar.vcs
View event previewBEGIN:VCALENDAR VERSION:1.0 TZ:+01:00 PRODID:-//Example organizer//EN BEGIN:VEVENT UID:studio-review@example.invalid DTSTART:20261116T093000 DTEND:20261116T100000 SUMMARY:Studio review LOCATION:Meeting room 2 DESCRIPTION:Review the sketches and agree on next steps. RRULE:W1 MO #4 END:VEVENT BEGIN:VEVENT UID:workshop@example.invalid DTSTART:20261119T140000 DTEND:20261119T160000 SUMMARY:Design workshop LOCATION:Studio DESCRIPTION:Bring your notebook. END:VEVENT END:VCALENDAR
Fictional example
2 events in this example. Repeating series appear once. Review dates, times and conversion notes.
2026-11-16 09:30:00 – 2026-11-16 10:00:00
UTC+01:00
Meeting room 2
Repeats every week on Monday; 4 occurrences total.
Review the sketches and agree on next steps.
2026-11-19 14:00:00 – 2026-11-19 16:00:00
UTC+01:00
Studio
Bring your notebook.
One ICS file with all converted events.
For vCalendar 1.0 files. Your original file stays unchanged. Already have an ICS file? Open it in the ICS Viewer.
The built-in example contains two fictional events: a weekly Studio review at 09:30 and a Design workshop at 14:00. Both use the source calendar’s UTC+01:00 fixed offset. You can inspect the VCS source, view the ICS contents, and download the example without choosing a file.
| In the VCS source | In the ICS download |
|---|---|
| vCalendar version 1.0 | iCalendar version 2.0 |
| Weekly Monday review, four times | The same weekly series and count |
| Calendar offset +01:00 | Fixed time zone UTC+01:00 |
| Event titles, rooms and notes | Included with the two events |
After loading your own calendar, choose Try example to explore this conversion. Your calendar and pasted draft stay in this tab; Restore your calendar brings them back. Clear removes both copies.
VCS exports may encode accented characters or non-English notes as quoted-printable text. The converter decodes supported character sets and writes UTF-8 ICS, so you can check the actual event text in the preview.
UTC, fixed offsets, and floating times are labeled beside each event. Supported basic repeat rules are converted, and each series appears once. Ambiguous or unsupported date rules stop conversion with a message identifying the affected event.
Legacy reminders, attendees, attachments, and unsupported fields are listed before download. Review and acknowledge those omissions to continue. Keep your source file as a backup. This tool creates a calendar copy; it does not synchronize accounts or send invitations.
On a computer, open Settings, then Import & export. Choose the downloaded ICS and select the destination calendar. See Google’s import instructions.
On Mac, open Calendar and choose File, then Import. In Outlook on the web, choose Add calendar, then Upload from file. Check dates and time zones after importing, especially for floating times or repeating events.
Import once into a separate calendar first. Repeated imports may create duplicates, and later changes to the original VCS do not update the imported events.
Choose Upload VCS and select one .vcs file, or choose Paste VCS, paste the complete calendar, and select Convert pasted VCS. Review the events and conversion notes on this page, then choose Download ICS. Import the result into a separate calendar and check its dates and times.
VCS usually contains vCalendar 1.0 data from an older calendar app, phone, or organizer. ICS uses iCalendar 2.0. The formats describe similar event information but use different conventions for repeat rules, text encoding, time zones, and reminders. This tool reads the VCS data and writes a new iCalendar file.
Renaming changes the filename, not the calendar format. A vCalendar 1.0 file can still contain old repeat rules or encoded text that an iCalendar importer does not understand. Use the converter to create an actual version 2.0 calendar, then check the preview before importing.
Yes. File reading, conversion, previews, and ICS generation happen on your device. No account, payment, AI credits, or extension is required. Calendar text and filenames are not uploaded to our server or an AI provider and are not saved in browser storage. Clear removes your current calendar and example backup. Refreshing restores the fictional example.
The download is an iCalendar 2.0 file that can be imported by these calendar apps. In Google Calendar on a computer, use Settings, then Import & export. In Apple Calendar on Mac, use File, then Import. In Outlook on the web, use Add calendar, then Upload from file. Import behavior varies by app; check a few events first. This tool does not connect to an account, send invitations, or synchronize future changes.
Supported basic vCalendar rules are translated to iCalendar repeat rules: daily, weekly, monthly by date or weekday position, and yearly by month or day of year. Compatible exception dates and additional dates are kept. The preview shows each series once. Nested rules, exclusion rules, and count-limited rules with several days or months stop conversion because old exporters can interpret their counts differently. Export these calendars as ICS from the original app.
UTC times and explicit numeric offsets are normalized to UTC. Local times with a calendar-level TZ offset keep their clock times with a fixed-offset time zone definition. A fixed offset does not follow daylight saving. Times without any zone remain floating and are clearly labeled. Legacy daylight-saving rules and named-zone parameters in VCS stop conversion; export those calendars as ICS from the original app.
For date-only events, the default treats the VCS end date as the last occupied day. The ICS end date is written as the following day. If your exporter already uses the first day after an event, choose that option in All-day end dates. The preview always shows the last occupied day. Timed entries marked as all-day by vendor-specific fields stop conversion when the date boundaries are ambiguous.
Legacy reminder fields, attendees, attachments, and unsupported event properties are left out. Any such omissions are listed beside the preview, and you must acknowledge them before downloading. Event titles, dates, supported repeat rules, locations, notes, and existing event IDs are converted. Calendars containing tasks or nested components stop conversion rather than producing an incomplete event-only file.
Use one VCS file or pasted calendar up to 1 MB, with no more than 1,000 events. The file must contain one complete vCalendar 1.0 calendar. Invalid dates, damaged encoding, unsupported repeat rules, or unsupported time zones stop conversion without offering a partial download. A failed replacement leaves the previous calendar unchanged. Export a fresh, smaller calendar from the original app and try again.