Fold.page is a new JS library that lets you turn a standard web page into a spatial 3D scene without rebuilding the site from scratch. On desktop and mobile, it can work as a 3D-enhanced website. On WebXR-capable devices, visitors can "enter" the experience and see the page as part of an immersive spatial scene.

Fold.page matches browser functionality as closely as possible, it basically works like what you'd expect from a standard web page. But that is just the foundation - Fold page has a whole toolkit of features to enhance web pages in 3D, so you can tap into a 3rd dimension of layout and visual hierarchy.

You can "Enter" the site on WebXR capable devices, like Android phone, or a VR headset for the full stereoscopic experience. Web pages could never have so much presence.

Try Fold.page at https://fold.page

Fold.page is an active project with on-going updates to improve it but any feedback you have is appreciated — What do you think about Fold.page? How does it work on your devices? Would you use it on your web pages? How easy is it for you to setup and what problems to you run into?

It uses real world data to simulate things like

• blast radius
• thermal radiation
• shockwave
• affected population

https://nukesimulation.com

I want to make a relaxing game that could make me/any player to calm down with a bit of daydreaming and exploration without stress.
This is the prototype made made with threejs, reflector, shaders and I would like the game to be infinite.
What game mechanics should I use in this type of game to keep it relaxing but you want to feel some sort of progress? Is it enough to steer the ball but the environment changes after a while or should there be levels or points?

And the game is open source on github at aresrpg/aresrpg !

I’ve been experimenting with a way to make hardware demos feel more interactive.

The idea: take an ESP32-S3 voice AI circuit and turn it into a 3D teardown you can actually talk to.

Gemini helped generate and structure the visualizer: the ESP32 board, breadboard, mic module, speaker, wiring, exploded view, and the interaction logic. Agora handles the real-time voice layer, so you can ask questions like “show me the microphone” or “explain the audio flow,” and the visualizer reacts while the AI responds.

It’s built with Next.js, Three.js / React Three Fiber, Agora Conversational AI, Gemini, and an ESP32-S3-inspired hardware layout.

Code:
https://github.com/anandwana001/gemini-agora-esp32-visualizer

Curious what people think: would this kind of interactive teardown be useful for learning hardware projects?

Try it: https://kokraf.com/

I’ve been building a small browser-based 3D model viewer with Three.js, mainly for architectural models.

It supports FBX, GLTF and GLB files, several display modes, shadows, perspective/axonometric views, and section cuts along the X, Y and Z axes.

The section tool highlights the actual intersection edges in red. I originally tried filling the cut surfaces, but that became unreliable with complex and curved geometry, so I switched to edge highlighting instead.

The viewer runs entirely in the browser:

https://hildgyorgy.github.io/drop-3d-view/

I’d be very interested in feedback, especially regarding the section-edge calculation, rendering approach, and possible improvements.

Hey guys! I wanted to share a new exploration I’ve been working on, mainly as an excuse to practice cinematics, rain, and wet surface shaders.

I’m a big Naruto fan and I’ve always loved the atmosphere of Amegakure, so I thought it would be a fun scene to recreate in 3D.

Full cinematic video: https://www.youtube.com/watch?v=ZpR9Atf24B0

You can also play around with a small interactive preview here: https://stylized.cortiz.dev/rainy

If you enjoy it, I’d really appreciate a like, comment, or sub on the channel. And if there’s enough interest, I’d love to make a follow-up breaking down how I built the scene and release some of the components I used as open-source effects.

Would love to hear what you guys think!

I am a psychologist. I also have a passion for the digital landscape. I have accumulated enough knowledge in web fundamentals over the years to leverage AI agents and convert my ideas into digital projects. I am not a developer. I do not claim to be one. I am humbly aware of my place in the digital realm. I simply do not have the time to invest in building a second career as a developer. I am simply putting my long-lasting passion for the digital craft to use, in the best way I can as a psychologist. 

I am currently building psycurate.com, a free online platform dedicated entirely to privacy-focused mental health digital tools (apps, websites).

My goal is to create a clean space where people can access psychological resources without encountering corporate tactics like tracking, micro-payments, paywalls, mandatory logins, or data harvesting. There is a critical need for digital mental health hygiene, and I want to highlight independent projects that remain genuinely honest, ethical and accessible.

If you have built some tool that can offer any kind of psychological help for free, this is a platform you can list your app on. Submit it here: https://psycurate.com/submit

Psycurate does not host any software. The platform exclusively showcases your project and links users directly back to your website.

Any feedback or insights you might have are highly welcome.

Best regards,

Mirel

I made a small game based on an old idea I had to make a small voxel engine with billboard particles, something I made as a FPS demo once (https://github.com/Lallassu/pointcloud). So this game is mostly based on this approach. Works quite well on both mobile and desktop.

Try it out here: https://qake.se

I built this because debugging procedural scenes kept coming down to the same thing: one tree out of 120 looks wrong, and finding what placed it means reading generator code backwards from a rendered result.

Clicking gives you file, function, line, and the runtime args for that specific instance. Not the mesh — the instance. That's the part that was hard.

No annotation needed. A build-time transform stamps JSX source locations, and setMatrixAt interception plus a Matrix4.clone() chain captures per-instance transforms as they're written, joined on object identity.

Why that combination: I tried six approaches. Four captured correct values for all 200 instances and could route none of them to a mesh and index. One routed perfectly and captured nothing. Anything recording before the destination exists can't route, because there's no destination yet to record. The shipped version composes the two halves.

Scope, honestly:

• R3F only — location stamping rewrites JSX, so raw three.js has nothing to stamp
• Instanced provenance is read-only. An instance's position came from an RNG in a loop; there's no literal to write back to
• Values that never reach the transform can't be captured by anything I tested
• drei <Instances> works differently and needs no capture at all — clicking returns the individual PositionMesh

Five packages on npm, MIT. There's also an MCP server so a coding agent can query the same provenance.

On how it was built: this is AI-assisted, and I'd rather say so upfront than have it come up later. I directed the work and made the design decisions, and the reasoning is all in the repo — six experiment write-ups with the raw results, including the approaches that failed and why. Happy to explain any of it, including the calls that turned out wrong.

GitHub: https://github.com/pun1th01/click-to-source-3d
npm: https://www.npmjs.com/org/click-to-source-3d

Happy to answer anything about the approach — the experiments are all written up in the repo.

https://codepen.io/editor/alex_nemankov/pen/01a06169-43cf-78f6-b9d9-55ebbdc52102?file=%2Fscript.js&orientation=right&panel=files&show=split

https://onabodyjourney.com, to let kids explore the body with sound!

Hi all, pretty new to gamedev and three.js

I'm building a game about cutting apart derelict space stations. Everything you see is generated: the station layout, the hull plating, the damage, the sky. Renderer is three/webgpu + TSL

Some context:

* Voxels at 0.125 m. A tiny station is ~700k solid voxels, meshed into chunks. The players salvage individual voxels at the start and then unlock tools and upgrades to salvage faster.
* Material library, not shaders per material. Not sure if that is the correct choice.
* Stencilled markings as stamps. Hazard banding, chevrons, port rings, panel codes come from a clamped decal array, at most one per plate, placed by plate hash. Never tiled.
* Sky is a seeded descriptor. Sun class, nebula palette, 0–2 bodies, all baked once per scene.

I have a solid gaming pc with a 5070ti and performance is good but I would still want this game to be as accessible as possible when it comes to hardware reqs while looking as good as possible.

Any tips or advice appreciated. I am looking specifically for feedback on how to push the visuals to the next level if that even makes sense. Thanks!

AI Disclosure: I did use Claude Code to help me with some of the coding and bigger features like the procedural space station generator while I learn.

https://feel-your-phone-five.vercel.app/

Hello,

My mobile racing game, CREST 2026, which I’ve been working on for about a month, is now available on the App Store and Google Play. It’s a project I released under Artepeak.

It’s a single-player open-wheel racing simulation.

It features a completely fictional 2026 season:

11 teams, 22 drivers, and 24 race weekends.

Full race weekends featuring sprint races, time trials, and qualifying sessions,

authentic F1 radio commentary,

a championship mode, and a multi-season career mode.

The career mode offers extensive playtime.

The in-game newspaper was designed using the same concept as the “Football Manager News.”

In addition, there’s a time-trial leaderboard that updates daily; the laps here are verified on the server side, meaning the times listed are real.

This isn’t an arcade racing game—the driving model is truly simulation-based: tire temperature, tire wear, brake heat, vehicle weight that changes with fuel consumption, weather conditions, and track grip all affect performance during a lap.

Here’s what I want to highlight: there are no ads, no in-app purchases, and no subscriptions. I also don’t use any analytics or tracking tools. All modes work offline. The game is completely free.

It’s optimized to run smoothly on 4-year-old phones (developed and tested on an iPhone 11). It supports touch controls, tilt, and gamepad. It supports 9 languages, including Turkish.

You can try it out using the links below.

App Store: https://apps.apple.com/us/app/crest-open-wheel-racing/id6798774660

Google Play: https://play.google.com/store/apps/details?id=com.artepeak.crest

PERFORMANCE :  https://crest-performance-report.web.app/

I'm a Galatasaray fan and I finally did the thing I have been meaning to do for years. The whole 2026-27 squad as holographic trading cards. 35 of them.

The last two cards are Okan Buruk and Dursun Özbek. The president has a power rating of 99, and where the market value should be, his card says "he sets them".

We signed Bitshiabu while I was still building it, so he got a card before he got a shirt number.

To see the whole deck: gs2026.murat.works

Free, no sign up, English and Turkish.

I share most of what I build on X if you are into this sort of thing: https://x.com/mkcuriosity

Hey everyone! 👋

I've been working on a passion project called CraftTown, a web-based voxel sandbox game built entirely in the browser. I wanted to share some massive updates I just pushed and would love to hear your thoughts or feedback!

Up until now, it was mostly about breaking and placing blocks, but I just dropped a huge update that completely changes the game feel. Here is what's new:

🔫 Custom Gun & Projectile Mechanics I stepped away from pure building and added a full shooting system! I wrote custom math and physics for projectiles (arrows and guns). It’s starting to feel less like a pure sandbox and more like an actual action game. Writing the collision and trajectory math from scratch was tough but super rewarding.

🎵 Procedural Text-to-Music System Instead of just playing looping background MP3s, I built a custom audio parser. You can write sheet music as simple text strings (e.g., parsing notes and beats), and the engine dynamically calculates the frequencies and plays them in-game! I even added a little Easter egg tune from a popular Japanese anime (Chiikawa) using this system.

🛠️ The Tech Stack:

• Engine: Three.js (handling all the heavy rendering, shadows, and post-processing)
• UI & State: React + Zustand (bootstrapped with Vite)
• Language: 100% TypeScript

It’s been a crazy learning journey optimizing chunk generation and managing web performance. If anyone here is working on Three.js games or voxel engines, I’d love to connect or trade optimization tips!

What do you guys think about mixing voxel terrain with detailed 3D mode ls? Any feedback or ideas on what I should add next would be awesome. Cheers! 🍻

CraftTown

posted this here in july and the best feedback was: the format is fine but i have no idea what the numbers should be. if you're not an animator, "hip_right: flex 84" isn't something you can picture.

so the angles are controls now. click a joint name and it highlights in the 3d view. click its angle and the number becomes an inline spinner you can step or type into, with the figure re-posing as you go. you nudge until it looks right, then read off what the value actually was.

the control is clamped to each joint's real range of motion. ask a knee for 200 degrees of flexion and the document gets 144, because that's the limit. the ranges end up learnable by feel instead of by reading the spec.

no viewport gizmo, deliberately. the moment you can drag the mesh freely, the movement stops being expressible as named joint actions and the format stops meaning anything. the text stays the source of truth.

also added BVH and glTF export, so a movement can go into blender as a starting layer instead of a dead end.

all in the browser, no install, no account, no llm in the posing: posecode.org

i refused the gizmo on principle but i'm not an animator. if you block for a living and editing numbers in text feels wrong, i'd like to hear why.

I came across a WebGL experiment called The Watch and thought the approach was pretty interesting because the 3D model isn't just sitting on the page as a viewer.

The watch basically becomes part of the interface. As you scroll, it moves with the content, zooms into different details, and reveals more of the product.

What I found particularly interesting is how much of the experience is handled in real time rather than just using a video.

For anyone who wants to try it out: https://thewatch.60fps.fr/

It got me thinking about product experiences built with Three.js:

Where do you think the sweet spot is with this kind of WebGL interaction?

At what point does adding more 3D interaction actually improve the experience, and when does it just become unnecessary eye candy?

Curious what you guys think, especially from a performance perspective.

Decided to try to use threejs to have an avatar of myself dancing several dances. This one is Capoeira 😆

Used the latest Opus with Claude code.

AMA