Where to Find and Run Art Projects From Around The World
Most people looking for Art Projects From Around The World end up on GitHub after someone mentions it on Twitter or a Discord server. The repository itself is a collection of generative art sketches, mostly built with p5.js, Processing, and a few WebGL experiments. It's not a single app you download and install. It's a repo full of code you clone, then run locally or drop into the p5.js web editor. You don't click a big green button and get an .exe. You go to the repository page, hit the Code dropdown, and copy the HTTPS URL. Then in your terminal: git clone [url]. The project structure is usually straightforward. There's a sketch folder with index.html and sketch.js at minimum, sometimes a data folder with assets or font files. If you've ever opened a Processing sketch before, you already know what this looks like. I ran into an issue last year where the artist had used a relative path for a custom font file, but forgot to include it in the commit. The whole thing broke in the browser because the font was loaded from a missing local path. The fix was just opening the sketch.js file, finding the createGraphics or loadFont call, and swapping in a system font temporarily. Not glamorous, but it happened more than once across different repos I pulled.
Running Things Locally
The most common setup I use is the p5.js web editor for quick runs without touching a server. You paste the sketch.js and index.html contents directly into the editor and it just works. For anything involving shaders or heavy WebGL though, that gets flaky. Node.js with a local server is the reliable path. A single command like npx serve or python3 -m http.server on the root folder and you're running at localhost:8000 or localhost:8080. Here's a practical detail people miss: the index.html file often has crossorigin attributes or references to external CDNs that break if you just double-click the file open in your browser. Browser security blocks local file requests for things like JSON, textures, or external script tags. That's why the local server matters, not just as convenience but as a requirement. You can't bypass it.
Customizing and Adapting
The real value isn't in running the default output. It's in tweaking parameters. Most of these projects use a config object or global variables at the top of sketch.js. Resize values, color palettes, noise scales, iteration counts. Change those first. If you want to modify the rendering pipeline itself, look for the draw() function and trace the variable dependencies backward. I once spent an hour trying to understand a fractal branch generator before realizing the recursion depth was controlled by a single integer variable named depth at line 12. Everything else was downstream from that. Color is another place where things go wrong. Some projects hardcode hex values inside the sketch while others pull from a palette array. If you want to re-skin a piece, check for both patterns. The ones that only do one tend to be easier to modify. The mixed approaches are a pain because you'll change the palette variable and the output still looks the same because there's a fallback color baked in elsewhere.
Get the Full Details
Pitfalls and What Doesn't Work
Not every project in these collections runs cleanly on modern browsers. A lot of them were written years ago when certain APIs behaved differently. I've seen multiple sketches fail on Chrome because they rely on deprecated canvas methods or older WebGL 1 patterns that weren't handled gracefully. Firefox sometimes runs them fine where Chrome chokes, which is annoying but predictable given how each browser's rendering engine has diverged. The other issue is dependency management. Some repos bundle their libraries in a lib folder, others expect you to have them installed globally, and a few reference unpkg or jsdelivr URLs that may no longer resolve if the artist stopped maintaining the project. If you clone something and get a 404 on a script tag, check the commit history to see when it was last updated. Anything older than two years is a gamble. If you want alternatives that ship as downloadable applications rather than raw code, there are desktop tools like TouchDesigner or openFrameworks with example projects, but those require heavier installs and steeper learning curves. For pure browser-based generative art you can actually tinker with immediately, the GitHub repos are still the most accessible path even with the friction involved.
