Blender fluid simulation vs browser

When Blender fits

Use Blender when you need fluid motion inside a modeled scene that also has geometry, cameras, lighting, and a rendered final image or video. Blender's fluid system, called Mantaflow since version 2.82, handles both liquids and gases through two different solver types inside the same framework.

Setup takes real time, from building a domain object to tagging flow and effector objects, but you gain full integration with the rest of a 3D pipeline, including materials, compositing, and render engines like Cycles or EEVEE.

What a Blender fluid workflow involves

A liquid or smoke effect in Blender moves through several concrete steps before it reaches a rendered frame.

• Mark a domain object that defines the simulated volume for the whole scene
• Mark other objects as flow, to emit liquid or smoke, or as effector, to collide with the fluid
• Choose Liquid for FLIP, a particle based solver good for splashes and pouring, or Gas for smoke and fire
• Set resolution, which trades simulation detail against bake time and memory use
• Bake the simulation, which writes a cache to disk and can take anywhere from minutes to many hours depending on resolution and domain size
• Light, shade, and render the baked result with Cycles or EEVEE to get the final frame or video

When the browser fits

Use Fluidsimulation.net when you want instant feedback, a shareable link, or a quick visual without opening a DCC app or waiting on a bake. The whole simulation runs live in a browser tab, with no project file, no render queue, and no domain setup.

Modes cover water, fire, ink, and calm looks, each a different starting preset on the same real-time solver described in how WebGL fluid simulation works.

Blender and browser fluid, side by side

Here is the same split in one list.

• Setup: Blender needs a domain, flow objects, and solver settings. Browser fluid is ready the instant the page loads
• Wait time: Blender bakes can run minutes to hours. Browser fluid updates every frame with no bake step at all
• Output: Blender produces a rendered image or video you can composite into a shot. Browser fluid produces a live, interactive canvas or a quick screenshot
• Integration: Blender fits into a full 3D pipeline with cameras and materials. Browser fluid is a standalone 2D dye field with no 3D scene
• Control depth: Blender exposes viscosity, surface tension, and detailed solver settings. Browser fluid exposes a smaller set of real-time sliders covered in fluid simulation controls
• Access: Blender is a free download you install on a desktop. Browser fluid needs no install, just a modern browser

Choosing between them

For try-now play, a quick demo, or a motion reference, stay in the browser. For a shot that needs cameras, lighting, and a final render, keep Blender for the shot and use the browser tool only to explore motion ideas beforehand.