BlendedBoris Blog: Simple Blockchain Ownership Registration

Blender 5.3 Released: What Projects, Asset Library Extensions, Stable Saving and Gaussian Splats Mean for Artists Who Sell, License and Share Their Work (2026) | Blended BORIS | Digital Art IP

Blender 5.3 was released on 10 November 2026. The new version adds native Gaussian splats, an optional project system, a DLSS denoiser for the Cycles viewport, a stackable compositor, panoramic cameras in EEVEE, dispersion in Cycles, OpenTimelineIO support and a much reworked Video Sequencer. It also lets asset libraries be shipped as extensions, and the official Extensions platform now accepts libraries of public domain (CC0) assets.
On the same day, the Blender Foundation updated both long-term support lines: 5.2 LTS to 5.2.4 and 4.5 LTS to 4.5.16. Blender 5.3 is a regular release, not an LTS, so studios that need a fixed version for a long project can stay on 5.2 LTS while artists who want the new tools move up.
Most coverage focuses on render features, and those are real gains. For artists who sell, license or share their work, the quieter changes matter just as much: how project folders hold your files together, how asset libraries can now be distributed, which licence the official platform accepts for them, and a first step towards .blend files that stay byte-for-byte the same when nothing has changed. This article walks through what is new and what it means for your files, your licences and your proof of authorship.
TL;DR: Blender 5.3 for artists who sell or share work

Blender 5.3 (10 November 2026) brings native Gaussian splats, opt-in Blender Projects, asset libraries as extensions with optional access tokens, a viewport-only DLSS denoiser for NVIDIA GPUs, a compositor effects stack, EEVEE panoramic cameras and a better Video Sequencer. For creators, the key points are: the official Extensions platform takes only CC0 asset libraries, so paid packs need their own server and tokens; projects keep paths, libraries and colour settings together; packed data from indirectly linked files is no longer saved; and Grease Pencil Frame Duration is disabled. Back up files and test add-ons before you switch.

What is new in Blender 5.3?

The official Blender 5.3 release page lists DLSS denoising, Gaussian Splatting, Blender Projects, EEVEE Material Lighting nodes, dispersion in Cycles, OpenTimelineIO, a much improved Video Sequencer and Grease Pencil updates as the headline features. The developer release notes add the detail:
  • Gaussian splats. Splats from PLY and SPZ files, USD and glTF become a native point cloud type that renders in Workbench, EEVEE and Cycles. There is no splat export yet. We covered the details in our report on native splat support in Blender 5.3.
  • Cycles. A new DLSS denoiser for the viewport uses upscaling and reuses samples from earlier frames. It needs an NVIDIA GPU and driver 620 or newer. The Principled BSDF gains dispersion for glass and gems, and anisotropic roughness now works for transmission and the Glass BSDF. Texture baking is better on small and thin triangles.
  • EEVEE and viewport. EEVEE can render panoramic cameras, for example equirectangular and fisheye, though not yet with depth of field or raytracing. New Material Lighting nodes let a material control how it reacts to lights, which opens up toon shading and effects such as iridescence. Vulkan is now the default backend on Windows (not ARM) and Linux, with the minimum lowered to Vulkan 1.1.
  • Compositor. Effects can be stacked like Geometry Nodes modifiers, each one a node group feeding the next, and Bloom is available as a built-in effect. Seventeen Geometry Nodes now work in the compositor, and GPU playback can be up to twice as fast with the new caching.
  • Video Sequencer. Digital Production's overview lists ripple, shuffle and overwrite modes for moving strips, ripple trim and delete, initial OpenTimelineIO import and export, and optional hardware decoding.
  • Grease Pencil. New selection tools in Draw Mode, a Carver tool for cutting strokes and fills, and multi-region fills.

What are Blender Projects, and why do they matter for your files?

Until now, Blender had no idea that a set of .blend files belonged together. In 5.3, a folder becomes a project when it contains a .blender_project directory at its root. Files inside that folder share a few things:
  • Path templates. Paths can use {project_root} and custom project variables, so textures, caches and renders can point to the right place on any machine where the project folder lives.
  • Project asset libraries. You can browse all assets in a project, or split a large project into several libraries.
  • Colour management. The project sets the OpenColorIO configuration: Blender's default, ACES 1.3, ACES 2.0 or a custom one.
  • Recent files and splash artwork for the project.
The system is opt-in. Nothing changes until you create a project, and per-project add-ons are not part of this release. For freelancers and small teams, projects solve an old problem: a client opens your file and half the textures are pink because the paths pointed at your own drive. With project-relative paths, the whole folder moves as one unit. That makes handovers cleaner, but it also means the folder now holds everything: source textures, references, caches and sometimes assets you licensed from others. Before you share or sell a project folder, check what is inside and whether your licences let you pass each item on.
Projects also make your working history easier to keep in one place. Our guides to Blender file management and saving and backing up Blender projects still apply, and a project folder is a natural unit to back up, version and timestamp.

How do asset libraries as extensions change sharing and selling?

In Blender 5.3, an extension can now be an asset library, or point to a remote one. Remote asset libraries can require an access token for browsing and downloading, and an extension can share the token from its extension repository. Assets in online libraries can also be replaced with versions for newer Blender releases, saved as separate files with a version tag such as my_asset@b5_3.blend. We explained the token system when it was merged in our report on Blender online asset libraries and access tokens.
The licence point is the one to read twice. The official Extensions platform now accepts asset libraries, but only of public domain (CC0) assets. The Blender manual's licence page says the required licence for assets is CC0. CC0 means anyone can use, change, resell and redistribute the assets without credit, and that includes using them as AI training data. Our guide to works free from copyright and CC0 assets explains what giving up those rights means in practice.
So there are now three routes for sharing assets in Blender, and they suit different goals:
RouteWho can get the assetsLicenceGood forWatch out for
Asset library on the official Extensions platformAnyone with BlenderCC0 requiredFree packs, portfolio pieces, community goodwillYou give up control, credit and training restrictions
Your own remote library or extension repository with an access tokenPeople you give a token toYour own licencePaid packs, client libraries, studio kitsTokens can be shared; you host and maintain the server
Project asset library inside a .blender_project folderWhoever has the folderWhatever each asset's licence saysTeam and client workLicensed third-party assets travel with the folder
Marketplaces (Fab, CGTrader and others)BuyersMarketplace licenceSelling to a wide audiencePlatform terms, AI clauses, fees
For paid work, the token route is the new option. A seller can offer buyers a library they browse directly in Blender's Asset Browser, with updates for newer Blender versions handled by the version-tagged files. But a token is a key, not a licence. Anyone who holds it can download what it unlocks, so tie tokens to buyers, be able to revoke them, and keep your licence terms separate and clear. A token also does not stop a buyer from redistributing files after download. Dated records of when you published each asset are what helps if copies turn up elsewhere.
Your assets. Your dates. Your proof.

BlendedBoris adds a blockchain timestamp to your Blender work from inside Blender, so you hold dated proof of when you made each model, material and asset pack, whichever way you share it.

👉 Protect your Blender work with BlendedBoris

Does Blender 5.3 change how .blend files are saved?

Two core changes affect the files you deliver and archive.
Stable saving. The release notes describe "initial support for keeping .blend files the same when opening and saving a .blend file." Without it, opening and re-saving a file can change its bytes even when nothing in the scene was edited. That matters for anyone who fingerprints files: a hash or a blockchain timestamp proves that a particular version of a file existed at a given time, and a file that keeps changing without real edits makes it harder to show that two copies are the same work. The word "initial" is important. Do not assume every file stays identical yet, and keep the exact file you timestamped.
Packed data in linked files. A linked packed ID is now treated as directly linked if a local ID or another directly linked packed ID uses it, and only directly linked packed IDs are written. Indirectly linked ones are no longer saved in the current file. This saves space in pipelines with many layers of linked files, but it means a file that once carried extra packed data from deep in a link chain may now rely on the source files. Before you send a packed .blend to a client or a marketplace, open it on a clean machine and check that nothing is missing.
Neither change adds authorship information to your files. If you want your name and licence to travel with exports, see the sister blog's guide to metadata and watermarking in Blender. Our report on the Content Credentials timestamp flaw explains why a label inside a file is not the same as independent dated proof.

Is the DLSS denoiser AI, and does it affect how you label your work?

DLSS is NVIDIA's neural upscaling and denoising technology. In Blender 5.3 it is a viewport denoiser in Cycles: it gives a cleaner interactive preview faster, and the release notes describe it for the viewport only. It does not generate content for your scene. That puts it in the same group as the existing OpenImageDenoise and OptiX denoisers, which our guide to denoising in Blender covers.
This matters because portfolio and marketplace sites now ask about AI. ArtStation's terms, for example, say noise reduction and upscaling on existing content do not make work created with generative AI, as we explained in our report on ArtStation's AI declarations. A DLSS preview of your own scene is not generative AI under that kind of definition. AI-generated textures, HDRIs or base meshes are a different matter, wherever they come from.

Should you upgrade to Blender 5.3 now?

For personal work, most artists will want the new tools. For paid projects already in progress, check a few things first:
  • Grease Pencil Frame Duration is disabled. End frames are converted to regular frames, with an empty drawing added, when a file is read. If your 2D animation relied on this, test a copy first. Our guide to Grease Pencil 2D animation covers the basics.
  • Add-ons. The default name property of PropertyGroup is now read-only, and the order of bpy.data.all_ids has changed. Most add-ons will not notice, but tools that rely on these may break. Test the add-ons you depend on, and see our guide to Blender add-ons and extensions.
  • Graphics backend. Vulkan is now the default on Windows (not ARM) and Linux. If you see drawing problems, update your GPU driver first.
  • Older versions. The release notes do not promise that files saved in 5.3 open fully in older versions. Keep a copy of each file in its original version before you save it in 5.3, especially for client work and anything you sell.
  • Long projects. 5.2 LTS keeps receiving fixes and was updated to 5.2.4 on the same day, so it remains a safe choice for work that must not change mid-way.

What should Blender artists do now?

  1. Back up before you switch. Keep a copy of every active file in its original Blender version before saving it in 5.3.
  2. Test your add-ons and Grease Pencil files on copies, not on live client work.
  3. Try a project folder for your next job, with project-relative paths, and decide which colour configuration it uses.
  4. Audit what travels with it. Before you share a project folder or packed file, list every third-party asset inside and check its licence.
  5. Choose a licence on purpose. Publish to the Extensions platform only what you are happy to give away as CC0. Our tips on Creative Commons vs copyright for Blender assets help you choose.
  6. Treat tokens as keys. If you sell a remote library, issue one token per buyer, keep a list and revoke tokens you no longer trust.
  7. Check packed deliverables on a clean machine before sending them.
  8. Timestamp key versions. Record dated proof of the exact files you publish or deliver. For important pieces, see our guide to registering artwork, 3D models and renders and the sister blog's guide to immutable proof of art creation.
If you buy assets as well as make them, our report on Megascans going free with new AI training terms shows why the licence of every asset in your project folder is worth reading.

Where does this fit in the bigger picture?

Today our sister sites looked at other cases where control over files and access decided who gets the value of the work:

Conclusion

Blender 5.3 is a big release for rendering, compositing and editing, and it is also a quiet turning point for how Blender work is organised and shared. Projects tie files, paths and colour settings together. Asset libraries can now be shipped as extensions, but the official platform takes only CC0 assets, so anything you want to sell or control needs your own server, tokens and licence. Stable saving is a first step towards files that keep the same fingerprint when nothing has changed. Back up before you upgrade, check what travels inside your folders, choose your licences on purpose and keep dated records of the work you publish.
Make every version provable.

BlendedBoris records a blockchain timestamp of your Blender work from inside Blender, giving you dated proof of authorship for your models, scenes and asset packs, so you can show they were made by you, and when.

👉 Get started with BlendedBoris

FAQ: Blender 5.3

When was Blender 5.3 released?

On 10 November 2026. The same day, Blender 5.2 LTS was updated to 5.2.4 and Blender 4.5 LTS to 4.5.16.

Is Blender 5.3 a long-term support release?

No. It is a regular release. Blender 5.2 LTS remains the long-term support line for work that needs a fixed version.

What are Blender Projects?

An optional system in which a folder with a .blender_project directory at its root becomes a project. Files inside share path templates such as {project_root}, project asset libraries, recent files, splash artwork and a colour management configuration.

Can I sell asset libraries on the Blender Extensions platform?

No. The platform now accepts asset libraries, but the required licence for assets is public domain (CC0), so anyone can use and redistribute them. To sell a library, host it yourself or use a marketplace, and protect access with tokens.

Is the DLSS denoiser generative AI?

It is a neural denoiser and upscaler for the Cycles viewport on NVIDIA GPUs with driver 620 or newer. It cleans up a preview of your own scene and does not add generated content.

Will my old files work in Blender 5.3?

Generally yes, but Grease Pencil Frame Duration is disabled and converted on load, and packed data from indirectly linked files is no longer saved. Keep a copy of each file in its original version before saving it in 5.3.

Can Blender 5.3 export Gaussian splats?

No. It imports splats from PLY, SPZ, USD and glTF, and renders them, but there is no splat export in this release.

How can BlendedBoris help?

BlendedBoris adds a blockchain timestamp to your Blender work from inside Blender, giving you dated proof of what you made and when.
2026-11-11 16:22 News