blender-web-pipeline
Blender to web export workflows for 3D models and animations. Use this skill when exporting Blender models to glTF for web, optimizing 3D assets for Three.js or Babylon.js, batch processing models with Python scripts, automating Blender workflows, or creating web-ready 3D pipelines. Triggers on tasks involving Blender glTF export, bpy scripting, 3D asset optimization, model compression, texture baking, or Blender automation. Exports models for threejs-webgl, react-three-fiber, and babylonjs-engi
Security Assessment
About blender-web-pipeline
The blender-web-pipeline skill provides workflows for exporting 3D models and animations from Blender to web-optimized formats, primarily glTF 2.0/GLB. It solves the problem of getting Blender assets ready for the web at acceptable file sizes and performance, covering export configuration, batch automation, and optimization for engines like Three.js and Babylon.js.
The skill documents the Blender Python (bpy) API for accessing scene data and driving exports, a full reference of `export_scene.gltf` parameters, and recommended presets (minimal, standard, high quality) that trade file size against fidelity. It covers Draco mesh compression settings, texture optimization (atlasing, JPEG vs PNG, resolution targets, MIP mapping), polygon reduction via the Decimate modifier and retopology, LOD generation, and normal-map baking. It includes bundled Python scripts for batch export, LOD generation, and model optimization, plus a headless invocation pattern (`blender --background --python`) for processing many .blend files, and concrete web performance targets such as under 50k triangles, textures at 1024–2048px, and sub-2-second load times.
Target users are 3D artists, technical artists, and web developers building interactive 3D web experiences who need repeatable, automatable export pipelines rather than manual per-file exporting. Typical use cases include converting legacy formats to glTF, batch-processing asset libraries, compressing models for delivery, and preparing assets to hand off to Three.js, React Three Fiber, or Babylon.js. The scripts operate locally on Blender files and the filesystem with no network or credential handling.
FAQ
What output format does the pipeline target?
Primarily glTF 2.0, favoring the single-file binary .glb form for web delivery, with support for separate and embedded glTF variants as well.
Can I process many models at once?
Yes. It includes a batch export script and a headless invocation pattern (blender --background --python) to export or optimize all .blend files in a directory, plus scripts for LOD generation and model optimization.
How does it reduce file size?
Through Draco mesh compression, texture atlasing and compression (JPEG for diffuse, PNG for alpha/normal), lower texture resolutions, polygon reduction via the Decimate modifier or retopology, and removing unused data.
What are the recommended web performance targets?
Roughly under 5 MB per model (ideally under 1 MB), under 50k triangles, textures at 1024–2048px, minimized draw calls via atlases, and load times under about 2 seconds.
Which web engines does it integrate with?
It targets Three.js, React Three Fiber, and Babylon.js, exporting assets those libraries can load directly.
Install blender-web-pipeline
Quick Setup:
- Copy the skill folder to
.claude/skills/ - Claude will automatically detect and use the skill
Repository
freshtechbro/claudedesignskills