Skip to content
← All articles
Project introduction

My bloc fork: browsing S3 and MinIO from Blender

Listen to the audio story

Browsing the cloud from inside Blender · 1:46 · AI-written script, synthetic voices

Transcript

Ava: Imagine you're modeling in Blender, and your whole asset library lives in a cloud bucket. What if you could browse it like a folder, without leaving the program?

Andrew: That sounds handy. Is that what Antoine built?

Ava: He took an existing add-on, credited the original author, and explored it in his fork called bloc. It adds a panel inside Blender for browsing files stored in Amazon S3 or MinIO, which is a self-hosted alternative.

Andrew: Okay, but cloud storage doesn't really have folders, right?

Ava: Right, it only has long names, called keys. Think of a name like models slash chairs slash oak dot O B J. The add-on splits that name on the slashes and builds a nested tree, so the panel shows real-looking folders you can open and close.

Andrew: Clever. And how do you pick which cloud to talk to?

Ava: A connection object holds the provider, the endpoint, the bucket and the region. You can save several connections in the preferences and switch the active one. The artist stays in Blender, and the add-on turns each click into the right storage request.

Andrew: What about finding things in a big library?

Ava: There's fuzzy search. It scores file names and path pieces, puts exact matches first, and has filters for scenes, meshes, images and materials. Typos still find your file.

Andrew: And when you click an asset?

Ava: It downloads to a temporary spot, then Blender's own importer opens it. Formats like S T L, O B J, P L Y and U S D are supported. There's also an option to upload the current blend file back to the bucket.

Andrew: So it's a bridge between a graphics tool and a platform service.

Ava: Exactly the mix Antoine enjoys. The full write-up has the diagram of the browse and import paths.

My bloc fork: browsing S3 and MinIO from Blender
Table of contents

My bloc repository[1] is a fork of MrKuros/Blender-Cloud-Storage[2]. It keeps the upstream author credit and explores a Blender panel for browsing assets in AWS S3 and MinIO.

1. The browsing and import paths

flowchart LR
  Storage["S3 or MinIO"] --> Listing["Folder listing"]
  Listing --> Panel["Blender panel"]
  Panel --> Download["Download selected asset"]
  Download --> Import["Local Blender importer"]

Listing creates the panel’s folder view; loading an asset downloads its bytes and invokes a local importer. A listing refresh can therefore succeed while an import fails on an unsupported format. The background refresh hands UI updates back through Blender timers instead of treating the storage request as a UI operation.

Read the architecture note with the connection and import boundaries.

2. Make the connection explicit

addon.py[3] defines a CloudConnection property group with a provider, endpoint, bucket and region. Preferences hold multiple connections and an active connection index. The client setup chooses the S3 or MinIO path from that selection.

This is the part that interests me as both graphics and platform work: the artist works inside Blender, while the add-on translates those actions into object-storage operations.

3. Turn object names into folders

Object storage uses keys. The refresh operator splits those keys on / and builds a nested dictionary for the panel. Folder expansion is tracked separately, so the UI can browse a hierarchy without pretending it is a local filesystem.

CloudSearchManager adds fuzzy matching with RapidFuzz. It scores filenames and path segments, gives direct substring matches priority and supports filters for scenes, meshes, images and materials.

4. Downloading and importing are different actions

The download helper saves an object to a temporary local path. The load operator then selects a Blender importer for STL, OBJ, PLY or USD variants. Other extensions are rejected with a message. A successful transfer alone does not mean Blender has imported a usable object.

The upload-current-file operator sends the saved .blend file. Although the README discusses dependencies, I would verify texture packaging and relative paths before relying on this path to move a complete scene.

5. Keep the fork’s scope visible

The public upstream comparison[4] showed 10 commits ahead and 5 behind on October 23, 2026. The changed files include the add-on, packaging metadata and README. That describes repository history; it does not establish that upstream accepted those changes.

The source also uses a single S3 list_objects_v2 request, so buckets beyond one response need pagination work. These are the kinds of small workflow boundaries I want to keep visible when revisiting the project.

References

  1. antoinebou12. (). bloc. [Software repository] github.com.
  2. MrKuros. (). Blender-Cloud-Storage. [Software repository] github.com.
  3. antoinebou12. (). addon.py. [Source file or documentation] github.com.
  4. antoinebou12. (). upstream comparison. [Source file or documentation] github.com.

References use this article’s publication date.