Browser support and requirements

Last updated: 13 August 2026

The Timetable Maker runs on any current version of Chrome, Edge, Firefox, Safari, Opera and the Chromium-based mobile browsers, on desktop and on phones. Rather than publish a version matrix that would be stale within months, this page lists the browser features the tool actually depends on, and the specific places where behaviour differs.

What it needs

Requirement	Used for	If missing
JavaScript	The entire application	Nothing works; the page is empty of function
Local storage	Saving your timetable between visits	The tool still runs, but nothing is remembered after you close the tab
CSS Grid and custom properties	Laying out the schedule grid	The layout collapses; this rules out Internet Explorer entirely
Pointer events	Dragging events to a new time	Dragging is unavailable; times can still be changed in the event dialog
Blob downloads	All four export formats	Exports cannot be saved
Canvas	PNG and PDF export only	CSV and JSON still work
File reading	Importing a JSON timetable	Import is unavailable; the editor is unaffected

All of these have been standard across major browsers for years. In practice, if your browser has been updated at any point recently, the tool works.

Two libraries load from a CDN

PNG and PDF export depend on html2canvas and jsPDF, fetched from cdnjs when the page loads. Everything else — the editor, autosave, CSV and JSON export, and JSON import — is self-contained and keeps working if those files are blocked or slow to arrive.

This matters on school, university and workplace networks, where CDNs are sometimes filtered. If the image libraries are blocked you will see a message saying the library is still loading when you press PNG or PDF. CSV and JSON remain available, and JSON re-imports on any machine where the tool loads.

Known differences by browser

Safari clears stored timetables after about a week

Safari on macOS, iPhone and iPad removes site storage for sites you have not returned to in roughly seven days. This applies to the whole category of browser storage, not to this tool specifically, and it cannot be opted out of by a website.

What to do: if you use the tool occasionally on an Apple device, do not treat the browser as storage. Export a JSON file and re-import it when you come back — that file is unaffected by anything the browser does.

Downloads behave differently on iPhone and iPad

iOS handles file downloads through its own flow. Depending on your version and settings, an exported PNG or PDF may open in a preview or a new tab instead of saving straight to Files, and you then choose where to keep it.

What to do: if an export appears to open rather than download, use the share or save control in the preview to store it. The file itself is correct either way.

Private and incognito windows do not remember anything

Storage in a private window is discarded when the window closes, and some browsers restrict it while the window is open. The save indicator will show a dash rather than a check mark if a write was refused.

What to do: build the timetable, then export JSON before closing the window. Reopen it normally later and import the file.

Very large timetables strain older phones

PNG and PDF export renders the whole grid to an image at double resolution. On an older phone, a seven-day timetable at 15-minute rows across a long day can exhaust available memory, and the export may fail to complete.

What to do: show fewer days or use a wider interval before exporting, or export from a desktop browser. CSV and JSON are unaffected by size.

Content blockers can remove parts of the page

Aggressive blocking extensions occasionally intercept the CDN requests for the export libraries, and some block web fonts. Blocked fonts mean the grid falls back to a system typeface, which can change how an exported image looks.

What to do: if an export renders in an unexpected typeface, reload the page and allow it a moment to finish loading before exporting.

Fonts and non-Latin scripts

The editor offers font stacks covering Latin, Cyrillic, Greek, Arabic, Hebrew, Devanagari and CJK scripts, chosen in Settings. Each stack ends in a generic system fallback, so text remains readable even when no web font loads.

Because PNG and PDF exports capture the grid as it appears on screen, the typeface in your export is whichever font the browser had available at that moment. If a web font has not finished downloading, the export uses the fallback. Reload and let the page settle before exporting if the result looks wrong. There is more on how each export is produced on the export formats page.

Screen sizes

The layout adapts down to phone widths, where row heights shrink and day headings abbreviate. A seven-day timetable is legible on a phone but tight; the grid scrolls horizontally rather than squeezing columns past the point of readability.

For building a detailed schedule, a larger screen is easier. For checking one you have already made, a phone is fine — or export a PNG, which is fixed and readable at any size.

Something not working?

If the tool misbehaves on a browser that meets the requirements above, that is worth reporting. Include the browser, its version and the device, through the contact page. Current defects are tracked publicly on the known issues page.