Run Locally.

The entire point of tinyfiles.tv is that you can take the code with you. Here is how to run a work on your own machine.

No build steps. No runtime dependencies. Every JavaScript work is either a single HTML file or a ZIP containing one HTML file plus static assets. You do not need Node.js, npm, Webpack, or a local server to run it.

The Process

01

Download the file

On any published work page, click the Download Source button. You will get one of two things: a single .html file, or a .zip containing the HTML plus any static assets the work uses, like a creator.png. If it's a ZIP, unzip it before opening the HTML.

02

Open it in your browser

Double-click the index.html file. It will open in Chrome, Firefox, Safari, or Edge. That's it. The WebAudio and Canvas APIs will initialize immediately.

03

Read the code

Open the file in a text editor (VS Code, Sublime, Notepad). Because we strictly enforce unminified, vanilla JavaScript, you can read exactly how the audio synthesis, rendering loops, and physics engines work. Change a number, save the file, refresh the page, and see what happens.

Why No Local Server?

Modern browsers strictly control what JavaScript can do when you open a file directly via file://. Usually, they block external API calls, CORS requests, and sometimes WebAudio autoplay. Those restrictions exist to stop a page from reaching the network — so a page that doesn't reach the network isn't affected by them.

That's the design constraint every work is built to: nothing loads from the network at runtime. No remote fonts, no CDN scripts, no third-party fetches. Static assets live next to the HTML, either inline or in the same ZIP. When you double-click the HTML, everything it needs is already on disk.