Tissue, the Blender add-on for computational design, and the version you already have

Tissue already ships inside Blender, which is the whole point of the install step

Tissue is described as Blender's add-on for computational design, made by Co-de-iT. The unusual part of its distribution is stated plainly in the project description: Tissue is already shipped with Blender. A user installing Blender gets a working copy of this add-on without doing anything at all.

That fact reframes the installation question. There is no pip step, no build toolchain and no command to run. The work is a zip file handed to Blender through its own preferences panel, which is why the instructions are written as clicks in the interface rather than as shell commands.

The reason the project asks you to do this work anyway is stated without hedging: the author recommends updating the default version by downloading the most recent one manually, for more updated features and more stability. So the bundled copy is a starting point, not the target state. The audience is Blender users doing computational design work who need current features, and the decision they face is not whether to install an add-on but whether to replace the one that came with the application.

For teams that pin Blender versions in production, that distinction is the whole decision. A studio that standardises on one Blender build inherits whatever Tissue shipped with that build, and the add-on evolves on its own schedule.

The add-on is a flat set of Python modules with a manifest

The repository layout shows what kind of tool this is. There is no package index, no build script and no compiled extension directory. The tree is a collection of Python modules sitting next to a Blender manifest file, which is the layout Blender add-ons use.

__init__.py
blender_manifest.toml
config.py
contour_curves.py
curves_tools.py
dual_mesh.py
lattice.py
material_tools.py
numba_functions.py
polyhedra.py
tessellate_numpy.py
texture_reaction_diffusion.py
tissue_properties.py
utils.py
utils_pip.py
uv_to_mesh.py
weight_reaction_diffusion.py

The names give away the working areas without requiring the documentation. Geometry related modules cover contour curves, curves tools, dual mesh, lattice, polyhedra, tessellation and a UV to mesh conversion. Reaction diffusion appears twice, once as a texture module and once as a weight module. There is a dedicated material module and a properties module for the add-on's own settings, plus a numba_functions module and a numba-free tessellation module, which is the shape of a codebase that runs numerical work outside the render loop where it can.

A utils_pip module also sits in the tree, which suggests the add-on can pull Python packages at runtime. The project does not say which packages or under what conditions, so treat that as an open question rather than a feature you can count on.

Installing the zip through Preferences, one click at a time

There is no command line install for this project. The project gives four interface steps, and they are the whole procedure.

First, start Blender and go to Edit, then Preferences. Second, open the Add-ons preferences page. Third, click install and point Blender at the downloaded zip file. Fourth, and this is the step people miss, you may now see two different versions of Tissue, so you activate only the second one and ignore the first one.

The download itself comes from the GitHub releases page, and the project points at the releases list for the latest build under its Blender 5 heading. The zipped artifact is the one Blender expects.

There is one platform wrinkle worth planning around. On macOS the zip may have been extracted automatically, and the extracted folder will not work, so you have to zip the extracted folder again before the install step. That is a small annoyance, but it is the difference between an install that works and one that fails with an unhelpful error, so check what you actually have in the Downloads folder before opening Preferences.

Once the add-on is active, the reference for what it exposes is the Blender manual, not the repository. The project links the Tissue documentation for Blender's latest version on docs.blender.org, under the mesh add-ons section of the manual.

Why the add-on list shows two copies of Tissue

The fourth installation step is the one that produces the most confusion, so it deserves its own explanation. The project states that after installing the zip you may see two different versions of Tissue, and that you should activate only the second one and ignore the first one.

The cause is the combination of the two facts above. Blender already carries a bundled copy of Tissue, so the add-ons preferences page lists that one as well as the copy you just installed. Which of the two is the second entry, and whether the order stays consistent between installs, is not something the project documents, and that is the practical risk. If you activate the wrong entry you can end up running a version that predates the features you installed the zip for, with nothing on screen telling you which one is live.

The safest habit is to check the version number of the entry you activate against the release you downloaded, rather than trusting position in the list. The release titles carry version numbers and Blender targets, so the comparison is possible.

The alternative, and it is a legitimate one, is to leave the bundled copy alone and never install anything. You gain a guaranteed working state with zero install friction, and you give up the newer features and the stability improvements the author asks for. For a one-off modelling session that is a reasonable trade. For work that depends on recent additions, it is not.

Reaction diffusion appears twice, as texture and as weight

Two modules in the tree carry the reaction diffusion name, texture_reaction_diffusion.py and weight_reaction_diffusion.py. Read strictly as filenames, they describe the same technique reaching two different destinations in a Blender scene: one writing into a texture, one writing into weight data.

That distinction is where the interest lies for a computational design workflow, and it is also where the repository is quiet. The project does not explain what the reaction diffusion routines compute, what parameters they expose, or how the texture variant and the weight variant differ in the interface. What you can confirm from the file list is the shape of the feature area: diffusion results can land in a texture layer or in vertex weights, and a materials module exists alongside them.

This is a good example of where the documentation boundary sits. The Blender manual page for Tissue is the reference the project itself points to, so that is where the parameters live. The repository gives you the module map; the manual gives you the meaning.

For a reader deciding whether to try the add-on, the practical question is whether the Blender manual documents the current release or the one bundled with their Blender. The project describes the linked documentation as being for Blender's latest version, which is a hint to check the version pairing before you rely on any particular operator.

The gaps the project leaves for you to fill

Several things an adopter would want are simply absent from the project description, and pretending otherwise would waste your time.

There is no support matrix beyond the release titles, which mention Blender 5 and Blender 4.5 LTS, so compatibility beyond the two most recent targets is unstated. There is no changelog in the repository, no description of what changed between releases, and no issue triage policy beyond a request to report problems and feedback on the GitHub issues page. There is no documented way to roll back to a previous release, and no description of how to uninstall the add-on or the downloaded zip.

The licence is the gap that matters most for anyone outside a single user setup. The repository's licence field is unknown, so while the project describes Tissue as free and open-source, no licence identifier is recorded against the project. That is not a legal opinion, but it is a concrete fact to resolve before a company redistributes the add-on or ships work built with it, and the author is the person who can answer it.

The support and feedback channels are clear enough. The project asks you to report issues at the GitHub issues page to help keep Tissue stable and updated, and the author links a Patreon page where the same person shares tips about Blender, Tissue and scripting.

Version tags, release titles, and one inconsistency worth noticing

The recent release history is short and informative. The newest tag is v0-3-75, whose title reads Tissue v0.3.75 for Blender 5 and Blender 4.5 LTS, dated 2026-06-07. Before it come v0-3-74 and v0-3-73, both dated in February 2026, and their titles point at Blender 5.0.

One detail there deserves a second look. The v0-3-74 tag carries a title that names version 0.3.73, and the v0-3-73 tag does the same, so the tag names and the version strings in the release titles do not line up cleanly across the February releases. A project with an automated tagging workflow can produce exactly this, and it is not by itself a sign of anything wrong. It does mean that if you script a download by tag name, do not assume the tag string is the version your user will see in the add-on list.

The repository is not archived, and the last push was on 2026-06-07, the same day as the newest release. That is recent enough that the current release corresponds to the current state of the code, and it also means the version you install now is the one the author last worked on.

For an add-on that is distributed as a zip and installed by hand rather than pulled from an index, that coupling between a release and a commit matters more than it would for a library with a version resolver. You are the update mechanism.

Editorial conclusion

Adopt Tissue if you work in Blender and want the newest computational design features rather than the copy bundled with your Blender build, and install the release zip through the Add-ons preferences as the project describes. Do not adopt it expecting a documented API or a stable licence: the repository states no licence, and the reference documentation sits in the Blender manual rather than in the project. Before you build anything on it, check that the release you download matches your Blender version, confirm which of the two add-on entries in Preferences is the newer one, and read the Blender manual page for Tissue to see what the current version actually exposes.

Frequently asked questions

Official sources

1. alessandro-zomparelli/tissue on GitHub
2. Issues
3. README
4. Releases