Find out what will be magenta on the buyer’s machine before you sell the file, and fix it in one press.

What it catches

A .blend stores paths, not files. It opens perfectly for you because your textures are still on your disk; the buyer opens it and every surface is flat magenta. That is the most common reason a Blender asset gets refunded, and the author cannot reproduce it.

Getly Publisher reads the file the way a buyer’s Blender will, and Getly refuses to publish while any of these are true:

• A texture the file needs is neither packed into it nor present in the upload
• A reference is rooted in your own home folder — /Users/you/… or C:\Users\you\…
• A linked .blend is not included in the download, so the buyer opens empty collections
• The file contains nothing a buyer could use
• A file named .blend is not one
• An add-on’s blender_manifest.toml is missing required fields or a valid SPDX licence

Alongside those it makes twelve suggestions that never block you: a texture whose capitalisation only resolves on Windows, meshes with no material, a scene with materials but no light, a Python script flagged to run when the file opens, a large uncompressed .blend, archive junk, no readme, an image-textured mesh with no UV map, an unapplied non-uniform scale, textures over 4096, and node groups that depend on a third-party add-on.

“Blender already has Pack Resources”

It does, and a tool that only reports what File → External Data already reports loses to a menu item you have installed anyway. This one runs those steps in the right order in a single press — paths made relative before packing, so unpacking later leaves you a working path rather than the absolute one you started with — then tells you exactly what it changed. It never saves the file: you look at the result and save it yourself.

The check runs twice, on purpose

Inside Blender it can evaluate what no file reader can: whether Geometry Nodes builds the UV map downstream, what a texture’s real resolution is, whether a linked library still has anything using it. But it runs on your machine, where your textures obviously exist — so every path it checks resolves, including the ones that will not be in the upload. So it advises. Getly re-reads the bytes you actually uploaded and decides, resolving each texture reference against the files genuinely inside the archive.

What it does not do

It is not a virus scanner. It does not judge whether your asset is good, only whether it arrives working. It cannot tell whether a render matches your listing images — only that the file has no lighting to reproduce them with. And it is Blender only: there is a Unity version, and no Unreal plugin, Photoshop panel or Cinema 4D equivalent.

Requirements

Blender 4.2 or newer. It is an extension with a blender_manifest.toml, not a legacy bl_info add-on. GPL-2.0-or-later, which is what anything built on Blender’s Python API has to be — the source is readable and you may fork it. Every check runs offline with no account; signing in is a separate, optional step that only matters if you want to submit a draft without leaving Blender.