# Blender 5.3 Ships Native Gaussian Splatting — Here’s What Changed > Source: > Published: 2026-11-12 03:06:34+00:00 Blender 5.3 landed on November 10, and the headline feature is not the new Quad-Sphere primitive. It is this: you can now import and render 3D Gaussian Splats natively — no add-ons, no Python scripts — via **File > Import > Gaussian Splat (.ply/.spz)**. The AI-powered 3D capture format that spent two years living in Python scripts and GPU research labs just became a first-class citizen in the world’s most popular open-source 3D tool. For game developers, XR engineers, and anyone who needs to place CGI into a real-world environment, this warrants attention. ## Gaussian Splatting in 30 Seconds If you haven’t used it yet: Gaussian splatting (3DGS) reconstructs a 3D scene from photographs as a cloud of millions of soft, anisotropic 3D blobs called splats. Each blob encodes position, shape, opacity, and view-dependent color. No mesh, no textures in the traditional sense — just blobs rasterized directly to screen. That’s why it renders at 80–120 fps on a mid-range GPU, while the neural equivalent (NeRF) tops out at 3–5 fps for comparable quality. [3DGS already beat NeRF for practical use](https://pyimagesearch.com/2024/12/09/3d-gaussian-splatting-vs-nerf-the-end-game-of-3d-reconstruction/); Blender 5.3 is the mainstream confirmation of that outcome. ## What 5.3 Actually Supports — and What It Doesn’t Blender 5.3 supports importing splats from **PLY**, **SPZ** (all versions up to v4), and **glTF with the KHR_gaussian_splats extension**. Imported splats are stored as PointCloud objects, which means they’re compatible with Geometry Nodes — you can filter, transform, and procedurally modify them. All three render engines (EEVEE, Cycles, Workbench) handle splats natively. For the full technical breakdown, see the [official Blender 5.3 release notes](https://www.blender.org/download/releases/5-3/). The Blender team is refreshingly honest about the current state. From the release notes directly: relighting is “rudimentary.” There is **no export yet** — you cannot round-trip a splat back to PLY or SPZ after editing. The color pipeline is not fully correct (sRGB-trained splats don’t map perfectly to Blender’s linear rendering). Apply Transform doesn’t yet correctly update all Gaussian attributes. The developers themselves call this alpha status. It is useful today; it is not a production pipeline component yet. ## Getting Splats Into Blender You need a PLY or SPZ file first. The simplest capture workflow: shoot 100–200 photos of a space or object, upload to [Polycam](https://poly.cam) or [Luma AI](https://lumalabs.ai) (both have free tiers), and download the resulting file. For offline processing with more control, Postshot runs locally on Windows. File sizes run roughly 68 MB per million splats in PLY; SPZ compresses that significantly, which matters if you’re targeting web delivery downstream. ## What You Can Realistically Do Today The no-export limitation defines the boundary clearly. Here’s what works now: - **Look development and mixed scenes:** Import a scanned real-world space, drop CGI objects into it, and light everything together in EEVEE. This is the core use case — environment reference that actually matches how light behaves in the real space. - **Game dev previsualization:** Scan a real location with your phone, import into Blender, use as reference or moodboard for level design. Far faster than building proxy geometry from scratch. - **XR/AR prototyping:** Mock up AR experiences against real-scanned environments before committing to Unity or Unreal. Blender’s EEVEE preview is fast enough for quick iteration. - **Film and VFX:** Mixed CGI-plus-scanned-background compositing, now without an extra tool in the chain. What doesn’t work yet: exporting modified splats to game engines, building full asset pipelines on top of splat geometry, or using this for anything that needs a correct transform hierarchy. Those gaps will close, but they’re real today. ## The Rest of 5.3 Is Not Filler The other changes in this release are worth flagging even if Gaussian splatting takes the headline: - **Vulkan is now the default backend on Linux and Windows** (minimum: Vulkan 1.1). OpenGL remains a fallback. Linux users running AMD or Intel GPUs will see the most immediate difference. - **NVIDIA DLSS 4.5 Ray Reconstruction** arrives as a Cycles viewport denoiser — it upscales and reuses samples from previous frames, dramatically accelerating look development on NVIDIA hardware. Requires driver 620 or newer. - **EEVEE gains panoramic camera support:** Equirectangular, Fisheye Equisolid, Mirror Ball, and others. VR/360 renders are now first-class in the real-time renderer. - **Video Sequencer gets full ripple editing.** For anyone using Blender as an NLE, this has been a long time coming. ## Worth Upgrading Now? Yes — the Vulkan default and DLSS 4.5 denoiser alone justify the upgrade for Linux and NVIDIA users. The Gaussian splatting support is genuinely useful today for look dev and previz workflows; just don’t build production pipelines on it. The export gap is the main blocker for anything more serious. Watch the 5.4 release notes for that. [Blender 5.3 is available now at blender.org](https://www.blender.org/download/).