Scratch 4.0 represents a major step forward for the visual programming language, bringing modern performance and streamlined workflows to educators, students, and hobbyists. This release aligns with broader updates in the project timeline, focusing on reliability, creative expansion, and smoother classroom deployment.
Below you will find a clear overview of dates, goals, and improvements, followed by detailed sections that explore new capabilities, migration paths, and real-world usage patterns. The structured summary table highlights key milestones and technical shifts relevant to developers and institutions evaluating Scratch 4.0.
| Version | Release Channel | Date | Key Focus |
|---|---|---|---|
| Scratch 3.0 | Stable | January 2019 | Web-first, extensible blocks, tablet support |
| Scratch 3.1 | Stable | Mid 2019 | Minor bug fixes, extension polish |
| Scratch 3.2 | Stable | Early 2021 | UI cleanup, microphone support updates |
| Scratch 3.24 | Canary | Late 2023 | Preview of new runtime and block parser |
| Scratch 4.0 Canary | Canary | March 2024 | Engine upgrades, stricter block validation |
| Scratch 4.0 Release Candidate | Release Candidate | September 2024 | Final testing, documentation updates |
| Scratch 4.0 Stable | Stable | Planned 2025 | Broad availability, migration tooling |
Scratch 4.0 Roadmap and Release Strategy
The Scratch 4.0 roadmap reflects years of community feedback, with the team prioritizing compatibility while introducing a more efficient rendering engine. Early canary builds allowed advanced users to experiment with new features, and the release candidate phase tightened security checks and improved localization. Moving toward the official launch, the focus remains on minimizing disruption for existing studios and projects.
Project leadership has consistently communicated a cautious timeline, ensuring that each milestone is driven by measurable quality targets rather than arbitrary dates. This disciplined approach reduces the risk of regressions and gives institutions time to plan infrastructure changes. As the stable version approaches, documentation and training resources are being updated in parallel to support a smooth transition.
Behind the scenes, the engineering effort has been reworking the block execution layer and refining the asset pipeline. These technical foundations enable better performance on modest devices and open the door for richer media types. The Scratch 4.0 roadmap is thus both a technical upgrade and a commitment to long-term sustainability of the creative learning ecosystem.
New Features and Capabilities in Scratch 4. video extensions and sensors
Scratch 4.0 introduces tighter integration with external peripherals, making it easier to connect physical computing devices without custom middleware. Video sensing now supports higher resolutions and reduced latency, enabling more responsive interactive installations. These enhancements expand the platform's relevance beyond traditional screen-based animations into physical computing and data visualization.
The extension system has been redesigned for greater modularity, allowing developers to publish sandboxed extensions that load on demand. This reduces startup overhead for users who only need a subset of hardware support. Additionally, cloud-backed project storage has been refined, with clearer version history and rollback options for classrooms that rely on shared accounts.
Accessibility improvements include better screen reader support for the block palette and color contrast adjustments for the stage view. Keyboard shortcuts have been expanded, and customization options for interface scaling make Scratch 4.0 more usable on a wider range of devices. Together, these enhancements reinforce Scratch's role as an inclusive environment for beginner programmers.
Migration Guide and Compatibility Considerations
Projects built in Scratch 3.x can generally be opened in Scratch 4.0 without modification, though the runtime may suggest automatically updating certain legacy blocks. Before migrating an entire curriculum or studio portfolio, it is wise to test representative projects and extensions to confirm behavior matches expectations. Teams should pay particular attention to custom blocks and video sensing configurations, as these areas are most likely to show subtle differences.
The Scratch team provides an offline tester application that allows local validation of projects against the 4.0 runtime. This tool highlights deprecated block usage and offers migration suggestions, streamlining the transition for educators managing multiple classrooms. By following documented best practices, institutions can schedule migration windows that align with academic terms and avoid disruption.
Documentation for migration includes step-by-step conversion guides, example project comparisons, and troubleshooting notes for known edge cases. These resources are targeted at teachers, club organizers, and volunteer mentors who need reliable procedures when guiding learners through the update. Clear migration guidance reduces friction and helps the community adopt Scratch 4.0 with confidence.
Performance, Stability, and Platform Support
Scratch 4.0 delivers measurable performance gains on both desktop and mobile devices, thanks to a redesigned rendering pipeline that reduces CPU usage during complex animations. Memory management improvements prevent gradual bloat during long sessions, which is especially valuable in shared computer labs. The platform remains accessible on low-cost hardware, supporting broader access to creative computing education worldwide.
On the stability front, automated testing has been expanded to cover edge cases in event handling and coordinate precision. This reduces unexpected behavior during projects that rely on precise timing or rapid input sequences. The team has also hardened network interactions for cloud-based features, improving reliability in regions with variable connectivity.
Platform support now includes the latest versions of major operating systems, while maintaining compatibility with devices that run earlier, but still common, hardware configurations. Installation procedures have been simplified, with clear guidance for IT administrators deploying Scratch 4.0 in managed environments. These considerations make it easier to roll out the update across schools, clubs, and community centers.
Key Takeaways and Recommendations for Adoption
- Verify project compatibility using the offline tester before large-scale migration.
- Schedule rollout during maintenance windows to address issues without disrupting learning.
- Leverage updated documentation and training guides for teachers and mentors.
- Monitor extension behavior, especially custom and hardware-related extensions.
- Utilize cloud backup and version history to protect student work during transition.
FAQ
Reader questions
When did the public rollout of Scratch 4.0 begin?
The public rollout began in early 2025, following the release candidate phase in late 2024 and gradual canary deployment starting in 2024.
Will projects from Scratch 3.0 work directly in Scratch 4.0?
Yes, projects from Scratch 3.0 will open and generally run in Scratch 4.0, with the runtime prompting for automatic block updates when necessary.
Are extensions from Scratch 3.0 compatible with Scratch 4.0?
Most extensions remain compatible, though some may require updates to work fully with the new extension loading system and security policies.
What should educators do to prepare for migrating their curriculum to Scratch 4.0?
Educators should test key projects and extensions in the release candidate environment, review migration documentation, and schedule updates during low-impact instructional periods.