blender-export

Q: How do I install blender-export?

Run npx skills add https://github.com/roble3/cc-blender-skill --skill blender-export in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/blender-export/ (personal) or .claude/skills/blender-export/ (project).

by roble3Media & Creative

Export Blender scenes to glTF/GLB (web/AR), FBX (game engines), OBJ (universal), USD (VFX pipelines), STL (3D printing). Includes Unreal collision hulls and Multires normal-map baking for low-poly export, per-format settings, embed/unpack textures, axis conversion, polygon optimization (Decimate), and target-platform validation. Use whenever the user asks to "export this", "save as glTF / FBX / OBJ / STL / USD", "package for Unity / Unreal / Three.js / web / AR / 3D print", or any output format conversion. Make sure to use this skill even if the user does not say "export" — also covers "package this for the web", "make it work in Unity", "send to Unreal", "save for 3D printing".

Installs: 1.4K
Last 24h: +38
Trending rank: #4023
Security: Not audited

Install

Works with every agent the skills CLI supports.

npx skills add https://github.com/roble3/cc-blender-skill --skill blender-export

01
Install
Run the command in your project. The CLI asks which agents to install for.
02
Describe the task
Ask your agent for something this skill covers. It loads blender-export automatically when relevant.
03
Review the result
The agent follows the SKILL.md steps, scripts and references bundled with the skill.

SKILL.md

The instructions your agent reads when the skill is triggered.

MCP backend

Use when: Any export to a non-.blend format, packaging for game engines, web, AR, or 3D printing.

Before the first Blender call, read ../text-to-blender/references/mcp-backends.md. Prefer official MCP for shared capabilities; preserve the selected backend for the whole task. Tool names in recipes are client/legacy examples: map them through that reference and its agent-host guide.

Blender Export

Export to the right format with the right settings. Wrong format choice = days of debugging in the target platform.

Format decision tree

Where is this going?
├── Web (Three.js, Babylon.js, model-viewer, AR Quick Look) → glTF / GLB
├── Game engine (Unity, Unreal, Godot)
│   ├── Animated/rigged → FBX (or glTF for modern engines)
│   └── Static → OBJ or FBX or glTF
├── Apple AR (USDZ) → USDZ (special, see Recipe 6)
├── 3D printing → STL (geometry only, must be watertight)
├── VFX pipeline (Maya, Houdini, Nuke) → USD
└── DCC roundtrip → FBX (industry standard)

Quick rule for unknown target: glTF / GLB. Open standard, modern, universally supported.

Recipes

Recipe 1 — glTF / GLB export (web / AR / general)

import bpy

bpy.ops.export_scene.gltf(
    filepath='/tmp/output.glb',
    export_format='GLB',                 # single-file binary; preferred
    export_apply=True,                   # apply modifiers before export
    export_materials='EXPORT',
    export_image_format='AUTO',          # PNG; AUTO falls back to JPEG for opaque images
    export_yup=True,                     # Y-up convention (most engines / web expect this)
    export_animations=True,              # toggle off for static models
    export_morph=True,                   # shape keys
    export_skins=True,                   # armatures + weights
    export_normals=True,
    export_tangents=False,               # skip unless target uses tangent-space normals beyond standard
)

# Verify
import os
size_mb = os.path.getsize('/tmp/output.glb') / (1024 * 1024)
print(f"export:gltf {size_mb:.2f} MB")

glTF caveats:

Only Principled BSDF materials export cleanly. Procedural shaders are dropped or simplified.
Hard cap: 15 MB; soft target: 8 MB.
No KTX2 / Draco compression (unless target supports those loaders).
PNG textures only (max 1024×1024 typical).

Recipe 2 — Decimate before export (if too large)

import bpy

obj = bpy.data.objects['GEO-target']
if obj.type != 'MESH':
    raise ValueError('Decimation requires a mesh')
selected = list(bpy.context.selected_objects)
active = bpy.context.view_layer.objects.active
mode = active.mode if active else 'OBJECT'
try:
    if mode != 'OBJECT':
        bpy.ops.object.mode_set(mode='OBJECT')
    bpy.ops.object.select_all(action='DESELECT')
    obj.select_set(True)
    bpy.context.view_layer.objects.active = obj
    mod = obj.modifiers.new('Decimate', type='DECIMATE')
    mod.decimate_type = 'COLLAPSE'
    mod.ratio = 0.7    # keep 70% of faces; lower = more reduction
    bpy.ops.object.modifier_apply(modifier=mod.name)
finally:
    bpy.ops.object.select_all(action='DESELECT')
    for item in selected:
        item.select_set(True)
    bpy.context.view_layer.objects.active = active
    if mode != 'OBJECT':
        bpy.ops.object.mode_set(mode=mode)

print(f"decimated:{obj.name} verts:{len(obj.data.vertices)}")

Then re-export. Iterate ratio until file size fits target.

Recipe 3 — FBX export (game engines)

import bpy

bpy.ops.export_scene.fbx(
    filepath='/tmp/output.fbx',
    use_selection=False,
    apply_unit_scale=True,
    apply_scale_options='FBX_SCALE_ALL',
    bake_space_transform=True,        # critical: applies rotation to mesh
    object_types={'MESH', 'ARMATURE', 'EMPTY'},
    use_mesh_modifiers=True,
    mesh_smooth_type='FACE',
    use_armature_deform_only=True,
    bake_anim=True,
    bake_anim_use_all_bones=True,
    bake_anim_use_nla_strips=True,
    bake_anim_use_all_actions=True,
    bake_anim_force_startend_keying=True,
    embed_textures=True,              # critical: embed textures into FBX
    path_mode='COPY',
    axis_forward='-Z',
    axis_up='Y',
)
print('export:fbx')

Common FBX gotchas:

Model rotated 90° in target → check axis_up='Y', axis_forward='-Z'
Model 100× too large → Apply Transform on the object before export
Textures missing → embed_textures=True, path_mode='COPY'
Animation only plays one action → use NLA + bake all actions

Recipe 4 — OBJ export (simple / universal)

import bpy

bpy.ops.wm.obj_export(
    filepath='/tmp/output.obj',
    export_animation=False,
    apply_modifiers=True,
    export_eval_mode='DAG_EVAL_VIEWPORT',
    export_uv=True,
    export_normals=True,
    export_materials=True,
    export_triangulated_mesh=False,
    forward_axis='NEGATIVE_Z',
    up_axis='Y',
)
print('export:obj')

OBJ has no animation, no rigging, basic material support only. Use for simple geometry exchange.

Recipe 5 — STL export (3D printing)

import bpy

bpy.ops.wm.stl_export(
    filepath='/tmp/output.stl',
    ascii_format=False,    # binary STL (smaller, faster)
    apply_modifiers=True,
)
print('export:stl')

Critical for STL:

Mesh must be watertight (no holes, no flipped normals, no internal faces).
Pre-export: in Edit Mode, run Mesh → Clean Up → Make Manifold.
STL has NO units — most slicers assume mm. Set Blender scene units to mm before modeling.
STL has NO color/material — single-color grey only.

Recipe 6 — USD export (VFX pipeline)

import bpy

bpy.ops.wm.usd_export(
    filepath='/tmp/scene.usdc',
    export_animation=True,
    export_uvmaps=True,
    export_normals=True,
    export_materials=True,
    use_instancing=True,
    export_textures=True,
    overwrite_textures=True,
)
print('export:usd')

USD variants:

.usd — text-based (debuggable, large)
.usdc — binary (compact, fast — default choice)
.usda — ASCII (human-readable, larger)
.usdz — zipped USD with all assets (Apple AR / iOS)

Recipe 7 — Pre-export checklist (run before any export)

import bpy

# 1. Apply transforms (rotation + scale baked into geometry)
obj = bpy.data.objects['GEO-target']
bpy.context.view_layer.objects.active = obj
bpy.ops.object.transform_apply(location=False, rotation=True, scale=True)

# 2. Recompute normals
bpy.ops.object.mode_set(mode='EDIT')
bpy.ops.mesh.select_all(action='SELECT')
bpy.ops.mesh.normals_make_consistent(inside=False)
bpy.ops.mesh.remove_doubles(threshold=0.0001)
bpy.ops.object.mode_set(mode='OBJECT')

# 3. Apply modifiers (some exporters keep them, but for portability apply before export)
# Already done via export_apply=True / use_mesh_modifiers=True flags

# 4. Verify mesh stats
mesh = obj.data
print(f"export_check:{obj.name} verts:{len(mesh.vertices)} faces:{len(mesh.polygons)}")

Recipe 8 — Verify exported file

import os

filepath = '/tmp/output.glb'
if not os.path.exists(filepath):
    print(f"ERROR:not_found {filepath}")
else:
    size_mb = os.path.getsize(filepath) / (1024 * 1024)
    print(f"verified:{filepath} {size_mb:.2f}MB")

Always verify after export. Use the host's shell tool: ls -la /tmp/output.glb.

Recipe 9 — Unreal collision meshes

Export a separate collider with the render mesh in the same FBX. Its name must match the render mesh exactly: SM_Chair → UCX_SM_Chair_01, _02, and so on. For existing GEO- names, derive the collider name from that actual name; do not rename the render mesh just to fit an example.

Prefix	Required shape
`UCX_`	One closed, outward-wound convex hull
`UBX_`	Rectangular box, not deformed geometry
`USP_`	Sphere, not a stretched ellipsoid
`UCP_`	Cylinder with hemispherical ends

Use several simple hulls for concave props: one hull around a table blocks the space underneath. Derive positions from geometry, not hand-entered guesses. A face-plane convexity test alone accepts open or empty meshes; it is not an export gate. Use scripts/collision_preflight.py to inspect the evaluated collider, check names/closedness/winding/volume/convexity, and export only the intended objects. It rejects rather than repairs invalid geometry and preserves selection/mode.

import bpy, runpy
# Substitute the installed helper path; load inside Blender, not ordinary Python.
helpers = runpy.run_path('/absolute/path/to/blender-export/scripts/collision_preflight.py')
mesh = bpy.data.objects['SM_Chair']
colliders = [bpy.data.objects['UCX_SM_Chair_01']]
result = helpers['export_collision_fbx'](mesh, colliders, '/tmp/chair_collision.fbx')
print(result)

The primitive checks cover local-axis authored boxes/spheres/capsules; use UCX_ for shapes outside those constraints. Boxes/spheres are unsuitable for a non-uniformly scaled render object. Use a new output path rather than overwriting. Only one render mesh per collision FBX is supported by this helper.

Engine-side behavior is not yet validated. Epic documents these conventions, but an Unreal import must verify hull count, openings, scale, and collision before claiming engine acceptance. Missing custom collision may instead trigger automatic collision generation; do not assume every importer configuration behaves alike.

Recipe 10 — Multires: bake to the cage, then export

A live Multires modifier may export every evaluated subdivided face or omit sculpt geometry, depending on exporter settings. For a low-poly asset, bake the detailed surface to a normal map and export level 0. A 30-face cage at level 8 is approximately 2 million faces.

Use scripts/multires_bake_export.py for a single-material target with UVs, an active Image Texture holding a Non-Color bake image, and exactly one enabled Multires modifier last in the stack. The helper sets viewport level 0 before baking, keeps it there through FBX export, saves/connects the normal map, and then restores selection, active object, mode, bake settings, engine, and subdivision levels. Use a single-user material and bake image. It does not overwrite an existing normal connection or accepted output files.

import bpy, runpy
helpers = runpy.run_path('/absolute/path/to/blender-export/scripts/multires_bake_export.py')
result = helpers['bake_export_cage'](
    bpy.data.objects['GEO-target'], '/tmp/target_normal.png', '/tmp/target_cage.fbx')
print(result)

A saved normal map/material connection is the intended change. On failure, generated files remain failure evidence; the helper restores temporary state and removes its new normal connection. Use new paths for a retry. To include colliders, pass an export_fbx callback that calls export_collision_fbx inside this helper's level-0 context; see references/unreal-export.md. Do not re-export after subdivision levels have been restored, or add ordinary meshes to the bake selection.

The helper detects the installed 5.x/4.x bake-property layout rather than assuming a spelling. Live validation is on Blender 5.1.1; Blender 4.x and Unreal imports remain unverified. Normal maps preserve surface shading, not silhouette changes.

Polycount targets per platform

Platform	Target	Notes
Web (glTF)	≤ 30 000 tris	Mobile-safe
Hero web asset	≤ 60 000 tris	Desktop OK
Unity / Unreal hero	50 000–100 000 tris	High-end
Mobile game	≤ 10 000 tris	Per asset
AR USDZ	≤ 50 000 tris	iOS recommendation
3D print	unlimited	But export size matters

Common pitfalls

Symptom	Fix
FBX has no textures	Set `embed_textures=True, path_mode='COPY'`
Procedural material missing in glTF	Bake to image textures first; use only Principled BSDF
Game engine: model rotated 90°	FBX: `axis_up='Y', axis_forward='-Z'`; glTF: `export_yup=True`
Game engine: model 100× too large	Apply Transform; check unit scale
OBJ won't import elsewhere	Stick to ASCII filenames
STL won't print	Make Manifold; recompute normals
GLB > 15 MB	Apply Decimate (Recipe 2); reduce textures to 1024×1024
Bone count exceeded	Limit weights to 4 per vertex; reduce bone count
Animation didn't export	glTF: `export_animations=True`; FBX: `bake_anim=True`
Unreal: missing/wrong custom collision	Check names, convex closed hulls, and same-file selection (Recipe 9); inspect the import in Unreal
Multires bake fails with a misleading multi-resolution error	Keep Multires last and isolate the target selection (Recipe 10)
Baked normals disagree with exported cage	Set viewport level 0 before baking, not just before export
FBX unexpectedly contains millions of faces	Viewport `levels` controls evaluated Multires export, not `total_levels`
Unreal: no smoothing-group information	Use `mesh_smooth_type='FACE'`; then verify inside Unreal

When to load `references/overview.md`

Load when:

Multi-format batch export needed
Asset Browser / library override workflow
USDZ for Apple AR specifics
Game engine roundtrip troubleshooting (Unity/Unreal-specific quirks)
LOD generation strategy

The reference covers: per-format pitfalls, asset browser workflow, library overrides for production, USD composition, polycount targets per platform.

FAQ

What does the blender-export skill do?

How do I install blender-export?

Run npx skills add https://github.com/roble3/cc-blender-skill --skill blender-export in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/blender-export/ (personal) or .claude/skills/blender-export/ (project).

Which AI agents can use blender-export?

Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.

Is blender-export safe to install?

No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.

Who maintains blender-export?

It is published by roble3 in roble3/cc-blender-skill. It has 1,399 recorded installs.

More from roble3/cc-blender-skill

View all →

blender-modeling

roble3/cc-blender-skill

Create and edit 3D meshes in Blender — primitives, hard-surface modeling, mesh operators, modifier stacks (Bevel, Subdivision, Boolean, Mirror, Array, Solidify), bmesh-level edits, retopology basics. Use whenever the user asks to "make/model/create/build a 3D object", "shape/sculpt this", "add a cube/sphere/cylinder/etc.", "extrude/inset/bevel this face", "add a modifier", or any geometry-creation request that isn't a wireframe trace. Make sure to use this skill even if the user does not say "model" — also covers "make a sword", "build a chair", "add a door", "carve out a hole". Pairs with blender-materials for look-dev and blender-pro-workflow for full pipelines.

Media & Creative2.3K installs

blender-materials

roble3/cc-blender-skill

Create and assign PBR materials in Blender via Principled BSDF — metals, glass, plastic, fabric, skin, organics. Covers physically-based material recipes with real-world values, Coat layer (varnish/car paint), Sheen (cloth), Subsurface scattering (skin/wax), Transmission (glass), and procedural patterns (wood grain, marble, fabric weave). Use whenever the user asks to "make it look like X material", "give it a metallic finish", "apply a wood texture", "make this glass / plastic / brushed steel / leather / skin", or any look-development request. Make sure to use this skill even if the user does not say "material" — also covers "make it shiny", "matte finish", "looks like copper", "rough surface". Works with any geometry; pairs with blender-lighting (materials only look right under proper lighting).

1.7K installs

blender-rendering

roble3/cc-blender-skill

Render Blender scenes with the right engine and settings — Cycles for photoreal, EEVEE for speed/stylized, sample counts, denoising (OptiX/OIDN), light path tuning, color management (AgX/Filmic), file output (PNG/EXR/MP4), animation rendering. Use whenever the user asks to "render this", "produce an image", "render a frame / animation", "make a final image", "save the render", or any output-generation request. Make sure to use this skill even if the user does not say "render" — also covers "make a picture", "save the result", "produce a final image", "export as image".

Media & Creative1.4K installs

blender-animation

roble3/cc-blender-skill

Animate objects, cameras, lights, and properties in Blender — keyframes, F-curves, easing (Bezier, Linear, Sine, Bounce, Elastic), shape keys (morph targets / blendshapes / visemes), drivers (Python expressions on properties), NLA actions for reuse and layering. Use whenever the user asks to "animate this", "make it move / rotate / scale over time", "add keyframes", "loop / oscillate", "shape key / morph / blendshape", "visemes for lip sync", or any time-based property change. Make sure to use this skill even if the user does not say "animate" — also covers "spin it slowly", "make it wave", "fade in / out", "pulse", "facial expression".

Frontend & Design1.3K installs

blender-pro-workflow

roble3/cc-blender-skill

End-to-end production workflow guidance for Blender — the order to assemble scenes (block-out → camera → light → forms → materials → detail → render → composite → export), critique protocols, time budgets, and recovery patterns. Use whenever the user asks to "make a complete scene / hero shot / production-quality render", "what's the right order to do this", "set up a full pipeline", or has a multi-step request crossing modeling + lighting + materials + rendering. Make sure to use this skill for any request that spans multiple phases of 3D work, even if the user does not say "workflow" — also covers "make a final image of X", "produce a hero render", "professional-looking result".

Productivity & Automation1.3K installs

reference-to-3d

roble3/cc-blender-skill

Reconstruct Blender models from supplied reference sheets, branding templates, texture atlases, orthographic front/side/back/top views, or mascot/logo art where visual fidelity to the source is more important than a plausible generated object. Use when the user says the model must match a template, wireframe, texture pack, character sheet, mascot sheet, or brand asset exactly; also use after feedback like "does not look like the reference", "fit the texture 1:1", "wrong number of visible parts", or "compare against the template". Requires Blender MCP plus local Python with Pillow/OpenCV/numpy; pairs with blender-uv-texturing, wireframe-to-3d, blender-modeling, blender-materials, and blender-export.

Media & Creative1.3K installs

Popular media & creative skills

View category →

hyperframes

heygen-com/hyperframes

Read first to make, edit, animate or render any video with HyperFrames (HTML rendered to video), including launch films, explainers, music videos, charts, maps, vertical clips, title cards, captions and overlays. Holds the render contract, the work loop and what each kind of video needs.

Media & Creative1.2M installs

media-use

heygen-com/hyperframes

Get or make any media for a HyperFrames video - music, sound effects, images, icons, logos, voiceover, avatar and generated video, transcripts, cutouts, colour grades and looks - with HeyGen or free local tools, and mix placed audio. Also for footage that looks dark, flat or dull, or should be stylized or hidden.

Media & Creative1.1M installs

hyperframes-registry

heygen-com/hyperframes

About 450 ready-made HyperFrames blocks and components installed as editable source - transitions, overlays, titles, kinetic type, captions, charts, map overlays, 3D, camera moves. Use it before hand-building any named visual (CRT scanlines, glitch, film grain, a chart); also for hyperframes add and catalog.

Media & Creative1M installs

hyperframes-creative

heygen-com/hyperframes

Non-animation creative direction for HyperFrames videos. Use for design spec (frame.md / design.md) handling, palettes, typography, narration, beat planning, audio-reactive visuals, composition patterns, and brand / style decisions. For atomic motion patterns and scene blueprints, use hyperframes-animation.

Media & Creative916.5K installs

ai-video-generation

101-skills/superpowers

Generate AI videos with Google Veo, Seedance 2.0, HappyHorse, Wan, Grok and 40+ models via inference.sh CLI. Models: Veo 3.1, Veo 3, Seedance 2.0, HappyHorse 1.0, Wan 2.5, Grok Imagine Video, OmniHuman, Fabric, HunyuanVideo. Capabilities: text-to-video, image-to-video, reference-to-video, video editing, lipsync, avatar animation, video upscaling, foley sound. Use for: social media videos, marketing content, explainer videos, product demos, AI avatars. Triggers: video generation, ai video, text to video, image to video, veo, animate image, video from image, ai animation, video generator, generate video, t2v, i2v, ai video maker, create video with ai, runway alternative, pika alternative, sora alternative, kling alternative, seedance, happyhorse

Media & Creative881.5K installs

ai-image-generation

101-skills/superpowers

Generate AI images with GPT-Image-2, FLUX, Gemini, Grok, Seedream, Reve and 50+ models via inference.sh CLI. Models: GPT-Image-2, FLUX Dev LoRA, FLUX.2 Klein LoRA, Gemini 3 Pro Image, Grok Imagine, Seedream 4.5, Reve, ImagineArt. Capabilities: text-to-image, image-to-image, inpainting, LoRA, image editing, upscaling, text rendering. Use for: AI art, product mockups, concept art, social media graphics, marketing visuals, illustrations. Triggers: flux, image generation, ai image, text to image, stable diffusion, generate image, ai art, midjourney alternative, dall-e alternative, text2img, t2i, image generator, ai picture, create image with ai, generative ai, ai illustration, grok image, gemini image, gpt image, openai image, chatgpt image

Media & Creative880.3K installs

blender-export

Install

Install

Describe the task

Review the result

SKILL.md

MCP backend

Blender Export

Format decision tree

Recipes

Recipe 1 — glTF / GLB export (web / AR / general)

Recipe 2 — Decimate before export (if too large)

Recipe 3 — FBX export (game engines)

Recipe 4 — OBJ export (simple / universal)

Recipe 5 — STL export (3D printing)

Recipe 6 — USD export (VFX pipeline)

Recipe 7 — Pre-export checklist (run before any export)

Recipe 8 — Verify exported file

Recipe 9 — Unreal collision meshes

Recipe 10 — Multires: bake to the cage, then export

Polycount targets per platform

Common pitfalls

When to load references/overview.md

FAQ

More from roble3/cc-blender-skill

Popular media & creative skills

When to load `references/overview.md`