HopWorlds
Upload a GLB and turn it into a multiplayer 3D world you can walk through together.
Tagline
Turn any GLB into a shared world
Upload one. Walk through it together.
The fastest way to demo a GLB.
No build. No installs. Just shared walkthroughs.
The fastest way to turn a GLB into a shared 3D world.
The page is extremely focused on one workflow: upload a GLB, then walk through it with friends. That makes speed-to-demo the strongest category-defining story.
A lighter-weight alternative to building a custom Three.js or game-engine viewer.
For teams that only need to host and explore 3D scenes, HopWorlds appears to remove the need for engineering a bespoke viewer or packaging an engine build.
Kill the friction of 3D review: no installs, no builds, just shared walkthroughs.
The strongest pain-killer angle is about eliminating setup friction for collaboration. The site’s simplicity suggests it is designed for instant access rather than advanced editing.
Primary user
3D artists and indie creators who already export GLB models and want a fast way to share them interactively
ICP #1
Indie 3D artist publishing portfolio work on ArtStation or Sketchfab
Pain
They can show renders or embedded viewers, but not a true shared walkthrough where multiple people experience the scene together in real time.
Why this solves
HopWorlds lets them upload a GLB and immediately place the work into a multiplayer world, making portfolio reviews and demos feel more experiential than static galleries.
ICP #2
Creative technologist at a small studio building client-facing immersive concepts
Pain
They need to present environment concepts quickly without spending days setting up a custom WebGL app or game build.
Why this solves
The product’s upload-and-explore flow implies a faster path from asset to demo, which is ideal for client review cycles and internal walkthroughs.
ICP #3
Indie game developer sharing early scene blockouts with collaborators
Pain
They need an easy way for teammates to inspect spatial layout together without shipping a full build or managing engine-specific installs.
Why this solves
A browser-based multiplayer GLB experience gives collaborators a shared space to inspect scale, composition, and flow with minimal setup.
Strengths
- +The value proposition is instantly legible: upload a GLB, then explore it with friends.
- +The CTA hierarchy is clean with only two actions, which matches the product’s likely early-stage simplicity.
- +The tone feels confident and creator-friendly rather than corporate or overexplained.
Weaknesses
- −It explains almost nothing beyond the bare workflow, so users do not know what happens after upload.
- −There is no proof, no screenshots, and no example worlds, which makes the product feel untested despite the public landing page.
- −No mention of collaboration basics like invites, permissions, voice chat, avatars, persistence, or link sharing.
- −The page does not clarify GLB constraints, file size limits, or whether scenes need optimization.
- −The "v0.1 · phase 2 skeleton" note undercuts trust if shown to prospects instead of inside a developer-facing status area.
Fix these
- Add a visual demo above the fold showing two people walking through the same world in-browser.
- Spell out the collaboration mechanics: how users join, share links, and control access.
- Show 3-5 example worlds created from real GLB uploads to make the outcome concrete.
- Add a short "How it works" section covering supported file types, upload limits, and typical use cases.
- Reframe or hide the version/skeleton language from the main landing page unless targeting builders and early adopters.
Drop-in replacement copy
Headline
Upload one. Walk through it.
Turn a GLB into a shared world people can explore together in the browser.
Turn files into living demos
Upload a GLB and get a world you can enter right away. It makes 3D work easier to understand than a flat preview or a screenshot.
Review scenes together
Invite someone and walk through the same world at the same time. That makes feedback faster for artists, clients, and teammates.
Skip the build and install step
No custom viewer, no engine packaging, no local setup. Open a link in the browser and start exploring.
Browse what others have made
See example worlds and public uploads before you create your own. It helps people understand the output before they try it.
FAQ
What file types do you support?
Right now the core workflow is built around GLB files. If your scene exports cleanly to GLB, you’re in the target zone.
Do people need to install anything?
No. HopWorlds is browser-based, so collaborators join from a link.
Is this a 3D editor?
No. It’s for hosting, sharing, and walking through 3D worlds together. Think review and exploration, not scene editing.
Can I share a private world?
That should be part of the flow. The product is aimed at review and collaboration, so link sharing and access control matter.
What’s this best for?
Portfolio reviews, client presentations, early game environment blockouts, and lightweight shared spaces for creative teams.
GLB files are too static for reviews. HopWorlds turns one upload into a shared 3D world you can walk through together in the browser. No build. No install. Just drop in a GLB and send the link.
I kept seeing the same workflow: render screenshots, send a viewer link, wait for feedback. So I built HopWorlds. Upload a GLB. Open it in a multiplayer world. Walk through the scene with whoever needs to review it.
Client reviews should not need a custom Three.js app. If your team already exports GLBs, HopWorlds is the fast path from asset to shared walkthrough. Upload. Share link. Explore together.
This is what happens after upload: 1. Add a GLB 2. Get a world link 3. Walk through it with another person in-browser That’s the whole product. If you make 3D scenes, this is the easiest way to show them.
3D artists need better than a flat embed. HopWorlds gives them a shared space for walkthroughs, portfolio reviews, and scene feedback. The reaction I want is: oh, this is how 3D should be shared.
No installs for 3D walkthroughs. HopWorlds is a browser-based place to host GLBs and explore them with other people. Built for artists, game devs, and small teams who want a faster demo loop.
I built the thing I kept wanting for scene reviews. Take a GLB, put it in a world, share it instantly, and let people walk around together. If you’ve ever said “can you just open the file and look at it,” this is for you.
Waiting for a teammate to install a build is a bad 3D workflow. HopWorlds keeps it in the browser, so collaborators can inspect scale, layout, and composition right away. Less setup. More feedback.
Watch a GLB become a world people can enter together. That’s the pitch. Not a viewer. Not an editor. A shared place to test, present, and explore 3D work.
If your workflow starts with “here’s the file,” HopWorlds is probably the better middle step. It makes 3D review feel collaborative instead of passive. That’s the gap I wanted to close.
Angle: Pain-killer for 3D review friction
Most 3D review still starts the same way: - export a file - send a link - hope the other person can open it - ask for feedback over screenshots or a recorded video That workflow is fine for storage. It is bad for collaboration. I built HopWorlds because I wanted the next step to be simpler: upload a GLB, open a shared 3D world, and walk through the scene together in the browser. No installs. No build handoff. No “can you get this running first?” For indie 3D artists, game devs, and small creative teams, the fastest demo is usually the best demo. HopWorlds is early, but the use case is clear: make scene reviews feel live instead of passive. If you work with GLBs, I’d love to know what would make this actually useful in your workflow.
Angle: Fast path from asset to client-facing demo
There’s a hidden cost in 3D work that people outside the space underestimate: turning a finished asset into something other people can actually experience. A model can be done and still be hard to review. A scene can be ready and still be awkward to share. A concept can be strong and still lose impact in a flat viewer. That is the gap HopWorlds is trying to close. Upload a GLB. Get a world. Invite someone. Walk through it together. I’m not trying to replace serious tools, editors, or engines. I’m trying to remove the drag between “the asset exists” and “people can understand it.” If you are a 3D artist, a small studio, or a game dev doing early blockouts, this should feel obvious. The question I’m testing is simple: is “shared walkthrough in the browser” enough of a step up from static viewers to change how people review 3D work?
Angle: Build-in-public, product philosophy, and feedback ask
I’ve noticed a pattern in products people actually use: They do one thing. They do it fast. They reduce the number of decisions between intent and outcome. HopWorlds is my attempt at that for GLBs. Not a full editor. Not a giant metaverse platform. Not a complicated onboarding flow. Just: upload one, walk through it together. That’s the product philosophy. I’m interested in whether creators want this more than another viewer, and whether teams care enough about live collaboration to switch from their current workaround. If you export GLBs, I’d especially like feedback on: - what file limits would make this usable - what access controls you’d expect - whether sharing by link is enough - what would make this feel trustworthy for client review I’m shipping this in public and iterating from real use, not guesses.
No visuals for this kit yet.
Tagline
Upload a GLB. Walk through it together.
Description
HopWorlds turns a GLB upload into a shared 3D world you can explore in the browser with other people. Built for artists, game devs, and teams who want faster scene reviews without installs or custom builds.
Maker's first comment
I built HopWorlds because I kept running into the same annoying gap in 3D workflows: the asset exists, but getting someone else to actually experience it is still too much work. Screenshots flatten the scene, video is passive, and custom viewers or builds take time nobody wants to spend for a quick review. HopWorlds is my attempt to make that step boring in a good way. Upload a GLB, get a world, and walk through it together in the browser. I’m especially focused on creators who already export GLBs and want a faster way to share work with clients, collaborators, or teammates. I’d love feedback on what would make this genuinely useful for real 3D review: file limits, sharing flows, access control, and whether multiplayer exploration is enough to replace the usual viewer-plus-video combo.
Pinned maker comment
Would love feedback on whether the core loop is clear: upload a GLB, share a link, and explore together. If you work with 3D files, tell me what’s missing before this fits your workflow.
Meta
Your GLB review workflow is too slow.
Hypothesis: 3D artists and small studios will switch from static viewers to a browser-based shared walkthrough if setup is instant. HopWorlds turns one GLB upload into a multiplayer world you can explore together. No installs. No custom build.
Google Search
GLB viewer alternative for shared walkthroughs
Hypothesis: people searching for a GLB viewer want more than a render preview - they want collaboration. HopWorlds lets teams upload GLBs and explore them together in-browser, so scene reviews happen in real time instead of over screenshots.
Reddit Promoted
If your team exports GLBs, test this.
Hypothesis: indie 3D artists and game devs are tired of custom viewers, builds, and install friction. HopWorlds is a lightweight way to host a GLB as a shared world and walk through it with others in the browser.
Subreddits
r/SideProject
Show the product as a tiny, opinionated solution to a real workflow problem: GLB uploads becoming shared walkthroughs.
Rules: Share what you built, what broke, and what you learned. No pure promo; explain the problem and the process.
r/indiehackers
Post the build story: how you found the pain point, what the MVP does, and what you’re testing with early users.
Rules: Founders should share insights and numbers, not just a link. Be transparent about being early.
r/microsaas
Frame it as a narrow utility for a specific user: people who already export GLBs and need fast shared review.
Rules: Keep it concise, useful, and relevant to micro-SaaS builders. Avoid hype and broad market claims.
r/Sketchfab
Ask for feedback from people already publishing 3D assets: would they prefer a multiplayer walkthrough over a static embed?
Rules: Be respectful of creator workflows. Focus on usefulness to artists and not on growth.
r/gamedev
Show the scene review use case for indie devs sharing blockouts and early environment layouts.
Rules: Share a demo or technical explanation; avoid marketing language. The post must be valuable even if nobody clicks.
Communities
Post progress updates, user interviews, and launch learnings. Comment on threads about niche SaaS and creator tools before asking anyone to try HopWorlds.
Only post when you have a sharp technical or product angle, like browser-based multiplayer GLB walkthroughs. Keep the title factual and the comments honest.
Engage with 3D artists’ work first. Then ask a small number of creators if they’d try a shared walkthrough version of their uploads.
Discord servers for indie game devs and 3D artists
Join as a participant, not a promoter. Offer to run a live demo, ask for feedback on review workflows, and only share HopWorlds when someone asks how to try it.
Cold outreach template
Hey {firstName} - saw your {context}. I’m building HopWorlds, which turns a GLB into a shared 3D world you can walk through in the browser. If I sent you a link to test with one of your scenes, would you be open to quick feedback?
Product Hunt timing
Launch on Tuesday at 12:01 AM Pacific Time. That gives you a full weekday for Product Hunt traffic, and it fits a creator/dev ICP that tends to check new tools early in the workday rather than over the weekend.
Indie Hackers post ideas
- 01I built a multiplayer GLB world host because static viewers were killing my review loop
- 02What I learned talking to 3D artists before shipping HopWorlds
- 03How I’d get the first 100 users for a browser-based 3D walkthrough tool
Competitor alternatives
Current tone of voice
Minimal, playful, and product-led, with terse copy like "upload one. walk through it." and the self-aware label "v0.1 · phase 2 skeleton ·"
Your kit is ready. Sign up free to unlock, takes 10 seconds.
7 more X posts · 2 LinkedIn · Product Hunt copy · ad hooks · 100-user playbook · landing critique