Free 3D modelingsoftware, online.

Studio is a 3D workspace that runs in your browser — the place you assemble a whole shot rather than one asset. It has a real scene graph with parenting and transforms, polygon modeling on a half-edge core, a non-destructive modifier stack, curves with generators, cloners, keyframe animation on a timeline, PBR materials, cameras and lights, and a path-traced renderer. It is part of the Mixos suite, so a model can move between Studio, Mold (sculpting) and Paint (texturing) without leaving the tab.

Yes. Modeling, assembling, animating, rendering to the viewport and saving your scenes are free on every account, with no time limit and no watermark on your work. A paid plan (Pro, Max, or Team) is what unlocks taking files out — exporting a model, the scene file, a web build, or a rendered image. So you can take a scene from empty to finished before deciding whether to subscribe.

A browser with WebGPU — current Chrome, Edge, Firefox or Brave on Mac, Windows or Linux, or Safari 26+. There is nothing to download, no installer, and no plugin. Studio also runs on iPad, Android tablets and phones with a touch layout, and on Chromebooks whose ChromeOS provides WebGPU. If your browser can't provide WebGPU, Studio says so on arrival rather than failing halfway through your work.

For a lot of work, yes — scene assembly, polygon modeling, modifiers, curves and generators, cloners, keyframe animation, materials, lights, cameras and path-traced rendering are all here, with nothing to install and a scene that opens on any machine you sign in to. Blender still goes deeper on simulation, sculpting at extreme densities, video editing and the long tail of a twenty-year toolset. Studio trades that depth for zero setup, a browser that already runs on the machine you have, and an assistant that can drive the app for you.

Yes — GLB, glTF, FBX, OBJ and PLY. Every part arrives as its own scene object with the file's hierarchy and names preserved, and embedded textures come across with it and are stored with the scene. There are size and triangle ceilings; a file over them is refused outright rather than half-imported, because a partly-loaded scene is worse than none.

Models as GLB (one binary file carrying geometry, materials, textures and animation), glTF as a zip, or USDZ for Apple Quick Look. Renders as PNG stills or numbered frame sequences. Whole scenes as a self-contained HTML page, a CMS embed snippet, a react-three-fiber component or a vanilla three.js module. Exporting is the part that needs a paid plan — everything up to it is free.

Yes. Key transforms and parameters on a timeline, retime them in the dopesheet, and shape the interpolation in the curve editor with real tangents. Clips keep separate takes apart, and drivers link one value to another for the relationships a keyframe can't express. Finished animation exports inside a GLB, or renders out as a path-traced frame sequence.

Both, and they are the same renderer. The viewport can path-trace the scene exactly as assembled — your lamps, your materials, the world environment, through the camera you composed with — and a still re-accumulates from scratch at full output resolution and sample count. That takes real time (tens of seconds to several minutes), which is the honest cost of a physically-based image. A rasterized viewport render is there too when you want a full-resolution frame in under a second.

Yes, on any device whose browser provides WebGPU. Chromebooks run Studio's desk layout; iPads, Android tablets and phones get a touch shell where the viewport goes full-bleed and the panels become slide-up sheets from a bottom dock — one finger orbits, two dolly and pan. It is the same engine and the same scene, so one started on a tablet opens on a desktop exactly as you left it.

In your Mixos library, in the cloud — not in one machine's Downloads folder. Studio autosaves as you work, so a scene you started on one device is listed and openable on another, and you can always save an explicit version or a copy. A free account is what gives you the library.

Studio is where a shot gets assembled. Mold sculpts organic form and hands the mesh on; Paint textures the model with layered PBR materials; Blend mixes tileable surfaces and Auto textures a whole model from a prompt. Unwrapping and path-traced rendering happen inside Studio itself. A model moves between the apps in both directions without losing its texture, out of one shared library.

Studio is built on a command layer: every operation — toolbar, menu, keyboard shortcut, outliner drag — runs through one definition. The built-in assistant calls those same commands, so asking it to add objects, arrange, light, model or animate runs the identical code path your own clicks do. It reports the real result afterwards, including when the app clamped or refused something, rather than claiming it did what you asked.