---
title: Installation
type: introduction
layout: docs
parent_section: introduction
order: 2
---
This installation section will show several ways to get started with A-Frame.
Although many of the ways don't require any actual installation since A-Frame
is primarily HTML and JavaScript.
## Code Editors in the Browser
The fastest way to start playing from within the browser.
### Remix on Glitch
[glitch]: https://glitch.com/~aframe
[Glitch][glitch] provides an online code editor with instant deploying and
hosting of web sites. The editor supports both front-end and back-end code as
well as multiple files and directories. Glitch lets us remix (i.e., copy)
existing projects and make them our own and instantly host and deploy changes
for everyone to see.
[Hit **Remix** on this A-Frame project][glitch], mess with the HTML in
`index.html`, and see your site published live on each change! The base A-Frame
Glitch for example is published at `aframe.glitch.me`, but we will provide your
own custom URL name.
Below are a few other A-Frame Glitches for starters:
- [aframe-aincraft](https://glitch.com/~aframe-aincraft) - Minecraft demo.
- [aframe-gallery](https://glitch.com/~aframe-gallery) - 360° image gallery.
- [aframe-registry](https://glitch.com/~aframe-registry) - Showcase of various components.
- [aframe-vaporwave](https://glitch.com/~aframe-vaporwave) - Retro-futuristic scene.
- [networked-aframe](https://glitch.com/~networked-aframe) - Multiuser.
### Other Code Editors
Below are a couple other A-Frame starter kits on other browser-based code
editors. Both support remixing or forking:
- [Mozilla Thimble — A-Frame](https://thimble.mozilla.org/en-US/user/ngokevin/864056)
- [CodePen — A-Frame](https://codepen.io/mozvr/pen/BjygdO)
## Local Development
### Use a Local Server
For the options below, we should develop projects using a local server so that
files are properly served. Options of local servers include:
- Downloading the [Mongoose](https://www.cesanta.com/products/binary) application
and open it from the same directory as your HTML file.
- Running `python -m SimpleHTTPServer` in a terminal in the same directory as your
HTML file.
- Running `npm install -g live-server && live-server` in a terminal in the same
directory as your HTML file.
Once we are running our server, we can open our project in the browser using
the local URL and port which the server is running on (e.g.,
`http://localhost:8000`). Try *not* to open the project using the `file://`
protocol which does not provide a domain; absolute and relative URLs may not
work.
### Download the Boilerplate on GitHub
[ghpages]: https://pages.github.com/
The boilerplate contains:
- A simple HTML file that links to the [current version of A-Frame](#builds-prod)
- An optional local development server
- An easy deployment workflow for [GitHub Pages][ghpages] to share with the world
We can grab the boilerplate in one of two ways:
Fork on GitHub
Download .ZIP
### Include the JS Build
To include A-Frame into an HTML file, we drop a `
```
If we want to serve it ourselves, we can download the JS build:
Production Version 0.5.0 Minified
Development Version 0.5.0 Uncompressed with Source Maps
### Install from npm
We can also install A-Frame through npm:
```bash
$ npm install aframe
```
Then we can bundle A-Frame into our application. For example, with Browserify
or Webpack:
```js
require('aframe');
```
[angle]: https://www.npmjs.com/package/angle
If you use npm, you can use [`angle`][angle], a command line interface for
A-Frame. `angle` can initialize a scene template with a single command:
```sh
npm install -g angle && angle initscene
```