Timetable Maker Known issues, and how problems get fixed
Last updated: 13 August 2026
This page lists what is currently wrong with the Timetable Maker. Keeping it public is deliberate: a tool that claims to have no faults is either very new or not being looked at closely. If you hit something on this list, you are not doing it wrong.
How to report a problem
Send it through the contact page. A report is much easier to act on when it includes:
- What you expected to happen, and what happened instead.
- Your browser and whether you are on desktop or mobile.
- For export problems, which format, and roughly how large the timetable was — days shown, interval, number of events.
- If you can, an exported JSON file. It reproduces your exact timetable and settings, which usually turns a vague report into a fixable one.
How reports are prioritised
This is a free tool maintained alongside other work, so it would be dishonest to promise a fixed response window. What is fixed is the order things get looked at:
| Priority | What qualifies |
|---|---|
| 1 — Data loss | Anything that destroys or corrupts a saved timetable, or makes autosave fail silently. |
| 2 — Wrong output | An export that misrepresents the schedule: missing events, wrong times, mangled characters. |
| 3 — Broken function | Something that does not work at all in a current browser. |
| 4 — Rough edges | Layout problems, awkward behaviour, and inconvenience that has a workaround. |
Anything in the first two bands is treated as urgent, because both undermine the only thing a timetable has to do: be accurate. Privacy and data-rights questions are prioritised separately and always answered.
What happens after a fix
Every fix is written into the changelog with the date and what changed. If a defect on this page turns out to affect exports people have already downloaded, that is stated plainly in the changelog entry rather than quietly corrected — you should be able to tell whether a file you saved last month is affected.
Recently fixed
Fixed on 13 August 2026, in every language version. Full detail is in the changelog.
- Events crossing the edge of your visible hours were dropped from PNG and PDF. They are now drawn clipped to the window, with a dashed edge showing they continue beyond it. Events lying entirely outside your hours still cannot be drawn, but the tool now tells you how many there are instead of letting them disappear quietly.
- Ticking extra days while editing an existing event silently dropped them. Those days are now created, matching what already happened when adding a new event.
- Overlapping events covered each other. Events that overlap in time are now laid out side by side, so every one of them is visible and reaches your exports.
Open issues
PDF output is always one page
The PDF places the whole grid on a single A4 sheet, scaling it down to fit. There is no pagination, so a dense timetable — seven days, 15-minute rows, a long day — produces small text.
A failed image render can end without a message
If the PNG or PDF render fails partway — occasionally on very large grids, or under heavy memory pressure on older mobile devices — the download may simply never start after the "Rendering" message, with no error shown.
The last row can round when hours do not divide evenly
The number of rows is calculated by dividing your visible hours by the row interval and rounding. If the span is not an exact multiple — 07:00 to 21:30 with 60-minute rows, for example — the grid rounds to the nearest whole row, so it can extend slightly past your end time or stop just short of it.
Deliberate limitations
These get reported as bugs but are working as intended. They are listed here so you know they are not going to change soon.
- No account and no cloud sync. Timetables live in your browser and do not follow you between devices. Moving one means exporting JSON and importing it on the other device. This is the direct cost of not holding your data — the reasoning is on the your data page.
- We cannot recover a lost timetable. There is no copy on any server, so if your browser storage is cleared it is genuinely gone. Exported JSON is the only backup that exists.
- CSV cannot be imported. It is a one-way summary; JSON is the format that round-trips.
- Importing replaces your current timetable rather than merging into it, and there is no undo.
- Text in PNG and PDF is not selectable. Both are images of the grid, by design — it is what makes the multi-script font support work reliably.
- Events are stored per day, not as recurring rules. A class on three days is three entries, so changing the time means editing each one.
Something not on this list?
Then it is probably not known about yet, and a report is genuinely useful. The contact page is the fastest route. Details of how each export is built, which explains several of the behaviours above, are on the export formats page.