Skip to content

Instantly share code, notes, and snippets.

What would you like to do?
Start a dev server

Start a dev server

Serve a local directory of static assets - using one-line solutions and no scripts

The first solution uses an IDE extension, while the rest involve using the command-line (intended for macOS and Linux, but they will hopefully work on Windows too).

Table of contents

IDE extension

Install a live server extension for your IDE.

Most web developers tend to use VS Code, so I'll cover that.

  1. Choose one of these, go to the page, and click "Install" there.
    • Live Server extension. Supports a preview in your browser only.
    • Live Preview extension by Microsoft. Supports a preview in the IDE or in your browser. This actually uses the Simple Browser command which is already built-in to VS Code.
  2. Open your repo in VS Code.
  3. Start the server.
    • In the bottom right of the IDE, click the "Go live" button to start (or stop) the server.
    • Or open the command-prompt pop-up in the IDE and find one of:
      • "Live Server: Open with live server"
      • "Live Preview: Start server"
  4. Open your browser (this should launch automatically). For Live Preview, you can skip this step and use the preview pane in VS Code.


  • This works on any OS.
  • No environment set up needed. No need for installing or learning to CLI commands for runtimes (Node or Python), or any packages (like from NPM).
  • Includes hot-reloading - the browser will refresh to reload a page if you change a file. The Live Preview one even reloads on every change you type, without having to save.
  • Open a file like index.html before starting the server to get the browser to open there. Or you will get a folder view of your directory, which is also fine.
  • You might want to install a browser debugger extension for Chrome or Firefox so you can get your debugging in your IDE to work as usual.
  • Limitations:
    • This only works on port 5500 and requires to use VS Code as your IDE and have it open. The alternatives below can be run in a terminal anywhere by anyone (without VS Code installed), as long as they have the correct dependencies.
    • If your index.html page and assets are at the root of your repo, this works great. But this does not work properly if you have assets in a subdirectory because that extension will serve from the root. e.g. If your homepage is in public/index.html, then the browser will open at, then looking for /styles.css will fail. But, you can change the root - a way around this is to open your serving directory as a new window in VS Code. e.g. code public and then start the server in that window.


Install Python 3 - follow gist.

The Python CLI and the Python standard library are light and easy. No need to install a package or write a script!

Approaches to choose from using the http.server module.

  • Start in the current directory on port 8000 by default - view on http://localhost:8888.
    $ python3 -m http.server
  • Specify a port and restrict to localhost for security.
    $ python3 -m http.server 8080 --bind
  • Start in a subdirectory, such as docs here. The brackets makes the commands run in a subshell, so that you remain in same directory as before when the command is stopped.
    $ (cd docs && python3 -m http.server)

I like to alias the command like this:

alias pserver='python3 -m http.server'

Then run it:

$ pserver


There are many ways to do this.

Some popular options:

$ npx serve
$ npx sirv

Here are a couple of NPM packages you can choose from.


$ php -S


$ php -S localhost:8080 -t .


$ ruby -run -e httpd . -p 8080


These lists are more detailed and cover other solutions:

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment