Loading...
How it works
Schedules arrive as PDFs, photographs and screenshots — and then get typed into a calendar by hand, one event at a time. Doc2Calendar reads the document instead. Here is exactly what happens, including the parts that are harder than they look.
A PDF, a photo, a screenshot - a team roster, a term timetable, a shift rota, a court list, a conference agenda. Anything up to 5MB in PDF, PNG, JPG or WebP. There is nothing to format first and no template to fill in.
It works out what kind of document it is, then reads the layout - columns, tables, headers, handwriting - and pulls out each event's title, date, start and end time, and location. A schedule is rarely a tidy list, so understanding the shape of the page is most of the work.
Every event is shown before anything leaves the site. Fix a title, nudge a time, delete something that was never an event. Then download a standard .ics file and open it - the events land in Google Calendar, Apple Calendar, Outlook and 20+ more apps.
Reading text off a page is the easy half. The difficulty is that a schedule carries most of its meaning in its shape: a column header that applies to everything beneath it, a letter that stands for a twelve-hour shift, a year mentioned once in the title and never again. Two documents can contain the same words and mean entirely different things.
So the first thing it does is work out what it is looking at, then read it on those terms:
A roster saying 6:00 PM means six in the evening, wherever the person reading it happens to be. Convert that to a timezone and it drifts — the classic bug where a schedule imports three hours out. We keep the time exactly as the document wrote it, so 6:00 PM stays 6:00 PM on every device that opens the file.
“Every Monday and Wednesday until December” becomes one recurring event, not thirty separate ones. Your calendar understands it as a series, so moving or cancelling the whole thing is a single action rather than an afternoon of tidying.
Extraction is very good and occasionally wrong, and the honest response to that is to show you the result rather than hope. Every event appears in a list you can edit: change a title, correct a time, add a location, delete an entry that was a table header rather than an event.
A schedule stays in your account. Come back when a fixture moves, change it, and download the file again.
Turn on sharing and you get a link. Anyone who opens it can add the same schedule to their own calendar — useful for a team, a class or a family.
Worth knowing before you rely on it.
Typed PDFs and clear photographs are read accurately. Faint handwriting, heavy skew and poor lighting are where it struggles - and it will tell you it found nothing rather than invent events.
A date written 03/04 could be March or April, and no reader can be certain which. This is exactly why every event is shown for review before you export.
You get a file, not a subscription. If the original document changes, convert it again - the events are yours from the moment you export them.
Up to 5MB, one file per conversion. A very long document is read in full, but a fifty-page bundle is better split.
One credit converts one document, however many events are inside it — a fifty-event roster costs the same as a five-event one. New accounts start with three free credits, and credits are bought once rather than subscribed to. If a conversion finds nothing usable, you are not charged for it.
The document is read to extract its events and is not kept afterwards. The events themselves are saved to your account, which is what lets you edit, re-download and share them. Schedules are private unless you turn on sharing yourself.
The best test is the document you were dreading typing up. Three conversions are free.
Still deciding? Read the FAQ
If it has dates and times, Doc2Calendar can put it on your calendar.