For parents and teachers
G-Warp is a beta block-coding and game-making app. Learners build scripts by connecting blocks, draw costumes, make music, and experiment with animation. Its interface is G-Warp's own; Scratch/TurboWarp/PenguinMod compatibility is a goal, not a guarantee for every project or extension.
Classroom rule: the editor does not require an account for basic local use, but a project or feature may still contact external services. Before using G-Warp with children, test the exact build and features you plan to use and follow your school’s privacy rules.
Privacy: what we can and cannot promise
- No account is required to use the local editor. That is not the same as proving that no network requests happen.
- Do not enter or share secrets. Never put passwords, private keys, student addresses, school IDs, private URLs, or identifying information into a project, an AI prompt, or a bug report.
- Review before reporting. A bug report may involve GitHub and may include the information or files you choose to attach. Make a small, sanitized reproduction project and inspect it before submitting.
- Some features may use the network. Web project loading, extensions that use the internet, externally hosted resources, or any AI/service you intentionally configure can make network requests. Read each extension's description and warning first.
- We have not independently verified every outbound request for every feature in every build. Because of that, this guide does not claim that a specific category of data is “never sent” universally. Check the current build’s privacy/network behavior before a classroom rollout.
Children under 13
The project’s safety guidance says children under 13 should have a parent or guardian’s help/OK before sending personal information online. For a classroom, apply the school’s policy and obtain the required parent/guardian permission before using any online feature or asking children to submit reports. The safest default is to use sample names and avoid sharing personal data at all.
Suggested first lessons
1. Make G-Spark walk
Practise drawing a few poses, comparing them with Onion skin, and looping next costume with a short wait.
2. Build a clicker game
Introduce a score variable, click events and a sound effect. Learners can change the scoring rule after the basic version works.
6. Make falling stars
Teach clones and cleanup. Discuss why each temporary clone should eventually run delete this clone.
Before a lesson
- Open the exact version that students will use and test it with a sample project.
- Start with built-in blocks; avoid adding an extension unless the lesson needs it.
- Save a backup copy of any demonstration project. Have students use copies too.
- Explain how to Stop a running project, how to report a bug without personal details, and why an extension warning matters.
- Plan a no-network alternative if the class network or an extension service is unavailable.
Beta expectations
Controls, compatibility and edge cases may change. Test saving/reopening, the browser/PC you will use, and any sound/microphone or online feature before class. If something differs from the instructions, capture the build/version and simple steps; do not assume the learner did something wrong.
Read Safety + privacy → · Open the glossary → · All tutorials →