Library / SDK
playcanvas/supersplat avatar
playcanvas/supersplat

SuperSplat is a browser splat editor with a Rollup watch loop behind it

3D Gaussian Splat Editor

10,648 stars1,239 forksTypeScriptMIT

At a glance

What is it?
PlayCanvas SuperSplat is an MIT licensed, TypeScript editor for 3D Gaussian Splats that runs in the browser at superspl.at/editor. The hosted copy installs nothing, while the local build is a Rollup watch loop serving a dist directory, gated at Node 20.19, with cache clearing as a required step.
Who is it for?
SuperSplat suits someone who wants to inspect, edit, optimize, and publish Gaussian splats in a browser tab and can treat the hosted editor at superspl.at/editor as the real product. Before depending on it, confirm the operations you actually need are exposed in the current interface, because the repository page names four jobs without listing a single shortcut, accepted file format, or export target, and expect to read the User Guide rather than the source to find out.
Can I use it commercially?
Yes. MIT is a permissive licence: you can use, modify and sell software built on it, as long as you keep its copyright and licence notices.
Is it still maintained?
Yes. The repository last received commits 2 days ago.
What is it written in?
Mainly TypeScript, according to GitHub's language statistics.

Answers come from the project's GitHub data, last synced on November 15, 2026, and from our analysis. They are not legal advice.

From daily snapshots

Star history

  • playcanvas/supersplat10,648 ★ · +404
Star history
Repository2026-09-222026-11-15
playcanvas/supersplat10.2k10.6k

404 Stars in the last 54 days, measured from the daily GitHub snapshot. Compare with other projects

Editorial analysis

One npm script holds three processes open at once

Local development is a single npm entry that keeps several jobs alive together. `npm run develop` sets BUILD_TYPE=debug through cross-env, then uses concurrently with the --kill-others flag to hold `npm run watch` and `npm run serve` open side by side. The watch side is rollup -c -w, so an edit to the source triggers a rebuild, and the serve side is `serve dist -C`, which hands out whatever rollup wrote into dist. That --kill-others flag is why the pair behaves like one command: when either process exits, the other is taken down rather than left holding port 3000. The coupling reads well in a foreground terminal and poorly in a script, since there is no documented way to run the watcher on one machine and reach the served output from another.

Clearing the browser cache is a required step, not advice

Step four of the setup is not a suggestion. The instructions tell you to open a browser tab, disable network caching on the network tab, and clear the other application caches, then name `Cmd+Option+e` and Develop->Empty Caches as the Safari route. Whatever the browser already stored for localhost:3000 can survive a rebuild. A contributor who skips this and refreshes sees the previous bundle, decides the watch loop is broken, and goes hunting for a Rollup problem that was never there. The instruction names Safari specifically and says nothing about the equivalent controls in other browsers, so the same stale bundle trap is left sitting there for anyone who did not read the step as browser specific.

Running it yourself means provisioning Node before anything else

The hosted tool and the source tree describe two different products. The live version at https://superspl.at/editor inspects, edits, optimizes, and publishes 3D Gaussian Splats with nothing to download or install. Building it locally is gated on a version floor that appears twice: the setup asks for Node.js 20.19 or later, and package.json declares the same boundary in engines as >=20.19.0. The tree is not a thin shell around the hosted app either. Top level entries include copy-and-watch.mjs, rollup.config.mjs, eslint.config.mjs, and global.d.ts, so copy watching, bundling, linting, and ambient type declarations each live in a file of their own, with .github, docs, scripts, src, static, and test as the directories.

sh
git clone https://github.com/playcanvas/supersplat.git
cd supersplat
npm install
npm run develop

The auto-launch script depends on a Linux desktop helper

One convenience entry point is tied to a single desktop convention. `develop:auto-launch` runs concurrently with --kill-others around three commands: xdg-open pointed at http://localhost:3000/, then `npm run watch`, then `npm run serve`. xdg-open is the Linux desktop opener, so on macOS and Windows that first job has nothing to call and the browser never appears. Because --kill-others governs the whole group, the exit of any one of the three jobs takes the others down. Plain `npm run develop` avoids the whole question by not attempting to open anything, and the walkthrough documents only that variant.

A language lives in a JSON file and a TypeScript list at once

Localization is spread across two files and one query parameter. Strings sit as <locale>.json inside the static/locales directory, the locale codes themselves are registered in a list inside src/ui/localization.ts, and a translation is checked by starting the dev server and opening http://localhost:3000/?lng=<locale> with a code such as fr, de, or es. Adding a language is therefore a two file edit, and a locale dropped into static/locales without a matching entry in localization.ts never becomes reachable through that parameter. The scripts block carries lint:locales, wired to node scripts/check-locales.mjs, so the translation set has a checker.

The scripts block can lint and check locales, but it cannot run tests

build is rollup -c, watch is rollup -c -w, serve is serve dist -C, develop is the debug concurrent pair, develop:auto-launch adds xdg-open, lint is eslint over src and the config files, lint:locales is the locale checker, and test runs tsc -p test/tsconfig.json and then node --import ./test/register.mjs test/queue-ordering.mjs, so the one test script covers a single queue-ordering file. The most recent releases are v3.7.0 on 2026-10-26, v3.6.0 on 2026-10-21 and v3.5.2 on 2026-10-05.

Four jobs are named and no operation is documented

The project's own summary assigns four jobs to the editor: inspecting, editing, optimizing, and publishing 3D Gaussian Splats. Everything about carrying them out is pushed to the User Guide. The walkthrough covers Node, clone, install, run, and cache clearing, then hands the rest over. The README's WebMCP section lists tool areas including scene inspection, selection, editing, camera control, timeline and camera keyframe authoring, and import/export, but gives no keyboard shortcut, panel name, accepted file format or export target. That omission has a concrete cost for anyone evaluating the tool: you cannot tell from the tree which of the four jobs are exposed in the interface today and which live in the runtime serving https://superspl.at/editor. package.json does show the building blocks, with @playcanvas/splat-transform at 3.10.2 and @playcanvas/pcui at 6.1.4.

Editorial conclusion

SuperSplat suits someone who wants to inspect, edit, optimize, and publish Gaussian splats in a browser tab and can treat the hosted editor at superspl.at/editor as the real product. Before depending on it, confirm the operations you actually need are exposed in the current interface, because the repository page names four jobs without listing a single shortcut, accepted file format, or export target, and expect to read the User Guide rather than the source to find out.

Frequently asked questions

What is SuperSplat?

SuperSplat is a free and open source tool from PlayCanvas for inspecting, editing, optimizing and publishing 3D Gaussian Splats, described in the repository as a 3D Gaussian Splat Editor. It is MIT licensed and written in TypeScript.

Is SuperSplat free?

The repository calls it a free and open source tool under the MIT license. A live version runs at https://superspl.at/editor with nothing to download or install.

Can you run SuperSplat locally?

Yes, with Node.js 20.19 or later, which package.json enforces through engines >=20.19.0. Clone the repository, run npm install, then npm run develop, and open http://localhost:3000 with network caching disabled and the other application caches cleared.

How do you use the SuperSplat editor?

The repository walkthrough covers local development only: npm run develop starts the watcher and server, and source changes rebuild automatically once you refresh. Actual usage is pointed at the User Guide at developer.playcanvas.com/user-manual/gaussian-splatting/editing/supersplat/.

Is SuperSplat open source?

It is published under the MIT license with the LICENSE file at the repository root. Contributor graphics point at the contributors graph, and the project links a Discord, a Reddit community, and a PlayCanvas account.

Official sources

  1. License: MIT
  2. playcanvas/supersplat on GitHub
  3. Project website
  4. README
  5. Releases
Add this badge to your README

If you maintain this project, the badge below links readers to this analysis and shows its maintenance status from the daily GitHub snapshot. Paste the markdown into your README; add ?metric=license or ?metric=stars to the image URL for a different field.

Add this badge to your README

markdown
[![Hysen Labs](https://hysenlabs.com/badge/playcanvas-supersplat.svg)](https://hysenlabs.com/projects/playcanvas-supersplat)

Star history chart for your README

markdown
[![Star history](https://hysenlabs.com/chart/playcanvas-supersplat.svg)](https://hysenlabs.com/projects/playcanvas-supersplat)

Was this useful?