Pixton Troubleshooting

What you need to know first

Pixton’s own Technical Support section is five short articles: an error-reporting page, a domain allow-list, system requirements, one page on the Scene Maker not opening, and how to contact support. That is the entire vendor-documented surface for a browser application running on the least powerful devices in the building. These guides are the long version.

Most Pixton failures on a school network trace to the same fact: the app loads from several domains, not one. Pixton’s published allow-list has two entries that every student needs — *.pixton.com and fonts.gstatic.com — and fourteen more that educator accounts pull in for billing, support chat and error reporting. A filter that permits the main site and nothing else gives you a blank white frame with no error, because nothing on the page knows to report one.

The second family of problems is the device. Pixton sets browser minimums — Chrome 128, Edge 141, Firefox 144, and iOS 17.6.1 for iPads — and Safari does not appear on its supported list at all. Managed Chromebooks pinned to old releases fail silently. Low-memory devices running Pixton alongside a dozen other tabs crawl. Neither shows up as a Pixton error.

The third is the account, and Pixton names four specific scenarios for a Scene Maker that will not open: the Starter plan’s 40-project or 30-day limit was reached, the site was not refreshed after buying a subscription, an Educator account was converted to Solo Student, or the class was archived. Each has a specific fix, and none of them is a bug.

Every guide here starts with the fastest test that separates those three causes, then works through fixes in the order they actually resolve the problem — not the order the menus happen to be in.