3D Editor

3D Editor

Create and edit 3D scenes in your browser. Add primitives, transform objects, adjust materials. Export to GLTF/GLB. Free online 3D modeling tool

A 3D editor in the browser via Three.js / WebGL: place primitive shapes, position lights, navigate the scene with orbit controls, export to GLTF / GLB for use anywhere. This is not a Blender replacement — Blender has 30 years of features no browser tool can match — but for quick prototyping, learning 3D, or producing simple scenes for VR / AR / web, browser-based 3D is fast enough.

What you can build

  • Primitives — cube, sphere, cylinder, cone, torus, plane. The building blocks.
  • Position, rotation, scale per object — transformation gizmos like Blender / Maya / Cinema 4D.
  • Materials — basic (Lambert, Phong, PBR Standard) with color, roughness, metalness, normal maps.
  • Lights — ambient, directional (sun), point, spot. Shadow casting optional (expensive).
  • Camera — orbital navigation; orthographic and perspective modes.
  • Import GLTF / GLB — load pre-existing 3D assets to combine with primitives.
  • Export GLTF / GLB — standard 3D format that loads in Three.js, Babylon.js, Unity, Unreal, AR/VR viewers.

Working example: a simple product display

Input

Place a product (loaded GLB) on a pedestal under good lighting

Output

Scene:
  Plane (floor) — large flat plane, neutral gray.
  Cylinder (pedestal) — short, white, on floor.
  Imported product model — placed on top of pedestal, scaled to fit.

Lighting:
  Ambient light — soft fill (intensity 0.4).
  Directional light (key) — from upper-left, intensity 1.2, casts shadow.
  Directional light (fill) — from right, intensity 0.6, no shadow.
  Optional: rim light from behind (back light).

Camera:
  Perspective, 45° FOV, positioned to show product 3/4 view.

Export: GLB (single file with embedded textures), drop into an e-commerce site or VR viewer.

File size: typical ~500 KB-2 MB for simple scenes with low-poly product.

For e-commerce 3D product views, the standard pattern is: low-poly model + PBR materials + HDR environment map for realistic reflections. Browser 3D handles this well; viewers (model-viewer web component) embed the model with one HTML tag.

3D file formats and what each is for

  • GLTF / GLB — the JPEG/PNG of 3D. Standard for web, AR/VR, mobile. GLB = binary, single file. GLTF = JSON + separate textures.
  • OBJ — older, plain-text. Universal compatibility, but no animation, no PBR support, no compression.
  • FBX — Autodesk format. Common in game engines; can include animation. Proprietary but widely supported.
  • USDZ — Apple's format for AR Quick Look (iOS Safari). Mostly equivalent to GLB but specific to Apple's ecosystem.
  • STL — for 3D printing. Mesh-only, no materials or color (some extensions add color).
  • Blend — Blender's native format. Not standardized; only Blender opens it.
  • For web sharing in 2026: GLB. For AR on iOS: USDZ. For 3D printing: STL. For game engines: FBX or GLB.

When to reach for this tool

  • You are prototyping a 3D scene before committing to Blender / Maya / Cinema 4D.
  • You need quick product visualizations for a website without 3D specialist help.
  • You are learning 3D concepts (transforms, materials, lighting) hands-on.
  • You need to export a simple GLB for an AR view or VR scene.

What this tool will not do

  • It will not replace Blender. Mesh editing, sculpting, animation, particle systems, advanced shaders — Blender territory.
  • It will not render production-quality images. For final visualization, use a real renderer (Cycles, Octane, V-Ray) with longer render time.
  • It will not handle huge scenes. Hundreds of thousands of polygons start to slow even modern WebGL.
  • It will not do physics simulation properly. Rigid body, cloth, fluid simulation require dedicated tools (Blender, Houdini, Bullet).

Frequently asked questions

Can I import Blender files directly?

Not .blend. Export from Blender to GLTF / GLB / FBX / OBJ, then import. GLB is the recommended format — preserves materials, animations, textures in a single file.

How big a model can I work with?

Browser WebGL handles ~500k-1M triangles smoothly on modern hardware. Beyond that, frame rate drops. Optimization: decimate (reduce polygon count) before importing, or use LOD (Level of Detail) variants.

Does this work on mobile?

Yes, but slower. WebGL on phones is functional but limited; complex scenes lag. For touch-friendly 3D viewing on phones, prefer simple optimized models.

What is PBR?

Physically Based Rendering — materials parameterized by physical properties (roughness, metalness, base color, normal map) instead of arbitrary "shininess" values. Same material works across renderers. Standard since ~2015.

Can I animate 3D objects?

Basic transforms (rotate, translate over time) yes. Skeletal animation (rigged characters) requires the GLB to come with animation tracks already; the browser editor can play them but rarely create them. Use Blender or similar for animation creation.

Is browser 3D fast enough for games?

For 2D and simple 3D games: yes. For AAA-quality 3D games: not quite — WebGL/WebGPU are getting close to native performance but still trail. Most browser games stay in 2D / simple 3D territory.

Related tools

Last updated · E-Utils editorial team