›_Python & pipeline

bpy.data vs. bpy.ops, background renders, append and link, glTF export — running Blender from code and the command line. — 13 entries

bpy.data edits scene data-blocks directly. bpy.ops runs Blender actions and depends on the current selection and context.

Temporarily supplies the active object or selection an operator needs, without changing the user's current selection.

Blender evaluates and renders a scene without opening its window, which suits servers and batch jobs that produce files unattended.

Pass numbers, paths, and options at launch instead of editing the script. The -- marker separates Blender flags from script arguments.

A numbered set of still files displays one image per frame, for animated textures or for editing rendered frames later.

Reuse data from another .blend file: Append makes a local copy, while Link keeps a reference to the source library.

Export a scene to a 3D format suited to the web and game engines. GLB keeps mesh, material, and images in one file.

Create an FBX file shared by many 3D tools, often carrying meshes, armatures, and animation into game or motion pipelines.

Export a USD scene with a hierarchy of prims and references, useful for sharing complex scenes across DCC and render pipelines.

Read an object after modifiers, constraints, and animation are evaluated, for downstream calculations or exports that need the visible result.

Read repeated values such as vertex coordinates into a buffer in one call instead of looping through Python objects, useful for large meshes.

Run Python callbacks when events such as frame changes or file loads occur, for repeated tasks or synchronizing scene state.

An add-on extends Blender with Python. An Extension packages add-ons and other content for installation and updates through repositories.