# PlayCanvas > PlayCanvas is an open-source 3D engine for the web, rendering with WebGL2 or WebGPU, and a set of products built on it for games, product configurators, 3D Gaussian splat experiences and other interactive 3D in the browser. All PlayCanvas products are free and open source. The Editor is a hosted service that also offers [optional paid plans](https://playcanvas.com/plans). This is the entry point for AI agents. Each product below has its own index: read the index for your task, then fetch only the pages you need. Page links in the indexes point to Markdown versions of the pages. ## Rules 1. **Identify the authoring surface first, and use only its patterns.** The same engine is used in four ways: - **Engine**: code-first, with the `playcanvas` npm package or its CDN build. - **React**: `@playcanvas/react` components and hooks. - **Web Components**: `@playcanvas/web-components` custom elements in plain HTML. - **Editor**: the browser-based visual editor, where code lives in scripts attached to entities. In an existing project, `package.json` usually settles it: `@playcanvas/react` means React, `@playcanvas/web-components` means Web Components, and `playcanvas` on its own means Engine. Scripts synced from an Editor project, for example by the VS Code extension, belong to the Editor. 2. **Write new scripts as ESM scripts.** An ESM script is an exported class that extends `Script`, has a `static scriptName`, and declares attributes as class fields tagged `/** @attribute */`. In the Editor, the file must use the `.mjs` extension. Classic scripts (`pc.createScript` and `attributes.add`) are legacy but still supported: keep an existing classic script classic, and never mix the two formats in one file. 3. **Import engine names from `playcanvas`.** Write `import { Entity, Vec3 } from 'playcanvas'` and use the names directly: `new Vec3(0, 1, 0)`, not `new pc.Vec3(0, 1, 0)`. Use the `pc.` global only in classic scripts and in pages that load the engine with a `