Publish guide
Keep games simple, board-friendly, and free of private student data. A prompt-ready checklist is below.
Classroom-ready tips
- Large buttons and text readable from the back of the room
- Design landscape-first for interactive whiteboards and projectors
- No login or personal data collection inside the game
- For one-file games, embed styles, scripts and data for maximum reliability
- For multi-file games, upload a built folder as ZIP with exactly one HTML document named index.html
- HTTPS scripts and styles are supported in published games. Remote APIs are blocked; tracking, logins and personal-data collection are prohibited. Validation cannot prove third-party code is tracking-free, and external providers receive their own resource requests.
- Touch-friendly targets — many boards are giant touchscreens
- Choose a licence that matches how open you want remixing to be
Create a classroom game as ONE complete self-contained HTML file. Requirements: - Everything inline: CSS in <style>, JavaScript in <script>, data embedded. - Prefer embedded assets. If needed, use HTTPS scripts/styles only; no API calls. No server needed. - Landscape layout for an interactive whiteboard; big touch-friendly buttons. - Text readable from the back of a classroom. - Do not add logins, tracking, or personal-data collection. - Start from <!DOCTYPE html> and end with </html>.
What we accept
- One HTML document — paste it or load a local .html file, up to 50 MB.
- Normal game folder — choose your folder directly, including its images, sounds and other files. You do not need to make a ZIP or RAR. Choose the finished game folder with an index.html start page; up to 50 MB including file names.
- Browser-ready ZIP — include exactly one HTML document named index.html and relative non-HTML assets at the root or in one top-level folder.
- HTTPS dependencies — remote scripts, styles, images, fonts and media may load; remote APIs, secret keys, external embeds and server runtimes may not.
- Classroom-safe content — tracking, credential collection, student personal data, forced downloads, and attempts to leave the player are prohibited. Static checks cannot prove arbitrary third-party JavaScript is tracking-free.
Import an external creation
Choose Import external creation on Add creation. Paste the public HTTPS URL, choose how it should open, and add your title, creation type and learning objective. Check the link while signed out before publishing. A source-code export is not required.
The original provider controls availability and may block embedding. Open original remains available. URL versions preserve addresses, not copies of the remote content; download and native remix actions require uploaded source files.
Your game preview
After you save, ClassBoard opens your game securely on the server and creates a preview image automatically. You can leave the upload page once your game is saved. Some creations display a title screen until someone presses Play; that opening screen becomes the preview. You can also upload your own screenshot if you prefer.