Publish your work in real 3D

Using Folio

1. 1

   Create your account

   Your username becomes your public address: nextlook3d.com/folio/username. Lowercase letters, digits and hyphens.

2. 2

   Create a project

   One project per work. Give it a title — the web address is generated from it.

3. 3

   Upload your model

   Add a .glb file (up to 100MB). It is optimized right in your browser before upload — textures capped at 2048px, geometry compressed — and your original file is stored untouched, downloadable any time.

4. 4

   Add photos, videos and text

   Photos up to 10MB, videos up to 100MB. The summary appears on your portfolio card; the description tells the full story (line breaks are kept). Mark one photo as the cover.

5. 5

   Publish or hide

   Projects are public the moment you create them; use Hide for drafts. Your storage allowance is 5GB in total — remove old files to free space.

6. 6

   Customize your page

   In Settings: accent color, avatar, cover image, bio, links, and section order. The accent recolors your entire public page.

7. 7

   Work as a team, keep versions

   In a project’s Team panel, the owner invites classmates by username; they accept from their dashboard and can then edit everything except deleting the project. Every model upload becomes a new version — restore any older one, download its original, and show the whole timeline on the public page as your design evolution (or hide it with the History toggle). Always start from the latest version’s original, and see “Merging teamwork” below for combining parallel work.

8. 8

   What visitors can do

   Orbit (drag), move through the scene (right-drag), zoom without limits (scroll), re-center on any point (double-click). The Inspector panel adds wireframe, material channels and lighting environments.

Getting a GLB out of your software

Folio accepts glTF Binary (.glb) — the open standard for 3D on the web. Every major tool can produce one, directly or through Blender (free).

Merging teamwork into one model

Folio versions are whole files — it never combines two uploads by itself. The merge happens in your design tool, and every major tool can do it. The pattern is always the same: split the work spatially, bring your teammate’s part into your file, replace the stale copy, export one GLB, upload it as a new version. And first check the timeline: if nobody uploaded while you worked, there is nothing to merge — your file simply is the next version.

1. 1

   Split by zone, name things

   Agree who owns what (house, garden, site). Put each zone in its own collection / layer / group named after it — merging then means swapping whole zones instead of hunting objects. Structure the house itself the same way, per floor and room, so future merges can be as small as one room.

2. 2

   One person integrates

   Pick an integrator for each upload. Everyone else hands them their part — the source file, or their latest original downloaded from the version timeline.

3. 3

   Bring the parts together

   In the integrator’s file: import or append the teammate’s part, delete your outdated copy of that zone, keep theirs. Tool recipes below.

4. 4

   It works at any scale — even one room

   The merge unit is whatever your structure makes selectable: a zone, a floor, a single room, one chair. If a teammate reworked the living room, transplant just that — in the base file delete the old room’s objects, append/import theirs. Take the file with the most changes as the base and move the smaller change into it. A single fused “House” mesh cannot be partially merged in any software; if that happens, redo the smaller change on top of the other file.

5. 5

   Find out what actually changed

   Before merging, know the delta. Quickest check: open the project page in two browser tabs and pick two versions from the timeline to compare visually. In Blender, import both versions and toggle their visibility. And simply say it in the team — “I only changed the living room” saves an hour of hunting.

6. 6

   Check the seams, then export

   Where the parts meet (terrain edges, paths, shared walls), look for gaps or doubled surfaces. Then export a single GLB and upload it — the timeline records who merged what.

7. 7

   If you both touched the same thing

   Whether it’s one wall or a whole room, no tool resolves that automatically: open both versions side by side and pick per object, or redo the smaller change on top of the other file. Better: agree ownership up front so it never happens — this exact problem is why Revit and ArchiCAD have worksharing.

Make it look great in the viewer

• Delete what is not the project: kilometres of context terrain, floor-plan sheets laid beside the building, reference grids. The viewer frames everything you include.
• Avoid two surfaces at exactly the same height (a road strip lying in the plaza plane) — they flicker in every 3D viewer, including this one. Offset one by a few millimetres.
• Keep textures at 1–2K. Bigger is wasted — Folio caps them at 2048px on upload.
• Stay under roughly one million triangles for smooth orbiting on ordinary laptops.
• Check normals: faces that look dark from outside are flipped. Blender: Mesh → Normals → Recalculate Outside.
• Test before uploading: drop your .glb into any online glTF viewer — what you see there is what Folio serves.
• On shared projects, every file counts against the uploader’s own 5GB — old model versions included. Delete superseded versions you no longer need.