简体中文
EnglishHow forkphorus Compares to TurboWarp
Updated
For most people choosing between the two, TurboWarp is the better default: forkphorus's own page says TurboWarp "typically has better performance and compatibility than forkphorus and has an editor." forkphorus remains a reasonable choice if you want a lightweight player that compiles Scratch 3, 2, and 1 projects to JavaScript and you don't need an editor — but it is in maintenance mode, receiving only occasional bug fixes.
The comparison at a glance
| Dimension | forkphorus | TurboWarp |
|---|---|---|
| Primary purpose | Runs Scratch 3, 2, and 1 projects fast by compiling them to JavaScript | Runs Scratch projects with better performance and compatibility, plus an editor |
| Editor included | No editor described; it is a player with settings, embedding, and packaging options | Yes, includes an editor |
| Project support | Scratch 3, 2, and 1 (Scratch 1 via the scratch-sb1-converter library) | Not specified on the forkphorus page |
| Development status | Maintenance mode; occasional bug fixes only | Recommended by forkphorus as the alternative to try |
| Performance and compatibility | Fast compilation is its core feature | Described as typically better than forkphorus |
| Inputs for running a project | Project ID or URL, project file selection, drag-and-drop onto the page, or the examples studio | Not described on the forkphorus page |
| Embedding | Yes — embed the forkphorus player with options for autostart, light controls, hidden UI, and custom size | Not described on the forkphorus page |
| Packaging | Link to a web page that auto-runs the project; HTML/EXE/APK and other formats via the separate HTML packager | Not described on the forkphorus page |
| Turbo mode | Available as a packaging/player option | Not described on the forkphorus page |
| Renderer | WebGL renderer available under advanced settings (requires refresh) | Not described on the forkphorus page |
When forkphorus is the sensible pick
Choose forkphorus if your priority is dropping a project in and running it immediately with minimal setup, or if you specifically want its embed and package-link workflow. The page lays out a short path: paste a project ID or URL, select a project file, drop a file on the page, or open the examples studio. From there you can generate an embed with autostart, light controls, hidden UI, and a custom size, or get a link to a web page that runs the project automatically.
It also exposes player settings that are applied automatically: framerate (FPS), username, image smoothing, sprite fencing, and removing some limits. Advanced settings, including the WebGL renderer, require a refresh to take effect.
Two practical caveats come straight from the page:
- Unshared projects are no longer visible due to Scratch API changes. The page points to
https://docs.turbowarp.org/unshared-projectsfor workarounds. - Maintenance mode means you should expect stability rather than new features. Bug reports go through the linked problem-report option or the comments, for people without a GitHub account.
When TurboWarp is the better choice
Pick TurboWarp when you need an editor, when compatibility with a wider range of projects matters, or when performance is the deciding factor. The forkphorus page itself frames TurboWarp as the upgrade path, so treating forkphorus as a fallback for quick playback and embedding is consistent with how its maintainers describe it.
A concrete way to decide: if your task is "run this finished project fast and put it on a web page," forkphorus covers it. If your task is "open the project, change something, and then run it," forkphorus has no editor to offer, and TurboWarp does.
What forkphorus is built on
Understanding the stack helps set expectations. forkphorus is maintained by GarboMuffin and other contributors and is a fork of Nathan's phosphorus; its CPS-style compilation was inspired by Rhys's sb2.js. It uses JSZip to read .sb2 and .sb3 files, canvg to render SVGs for Scratch 2 projects, and scratch-sb1-converter to support Scratch 1 projects. Source code is on GitHub, and the page lists a privacy policy and a version stamp (e956580, dated 2026-10-25).
That lineage explains the feature set: a compiler-focused player with broad Scratch version coverage, not an authoring tool. If you need to package to HTML, EXE, APK, or other formats, the page directs you to the separate HTML packager rather than offering those exports directly.