We are not here to replace your work. We are here to give you the hours back.
You did not pick up Blender to rename four hundred objects or debug a driver expression. Loopcut does the technical side, in the open, one undo away, so you can spend your time on the part only you can do.
The honest version
The 3D community is right to be wary.
A lot of what gets sold as AI for artists is trained on artists' work and aimed at their jobs. If that makes you angry, good. It should.
Loopcut is a different bet. When we asked Blender artists where their time went, about 70% of it was technical: organising, fixing, wiring, exporting. Not sculpting, not animating, not deciding how a shot should feel. That technical share is where an assistant belongs, and it is the only place Loopcut works.
The creative call is yours. The scene is yours. The code is open. If we ever drift from that, you will be able to see it in the repository before we could announce it.
What Loopcut will not do
Four lines we do not cross.
Generate your art
There is no image or asset generator in Loopcut. It writes Blender Python against the scene you built. Your sculpt, your textures, your composition stay yours to make.
Act behind your back
The code for every step is on screen before it runs. You approve it, or you tell it to stop asking for this conversation. It never edits a file silently.
Take your scenes anywhere
With your own key or a local model, nothing touches our servers. With hosted models, the gateway relays your request and keeps token counts for billing. Not prompts, not scenes.
Lock you in
Open source, any OpenAI-compatible model, standard .blend files. If Loopcut disappeared tomorrow, your files and your workflow would be exactly where you left them.
What it will do
The chores you would hand to a TD, if you had one.
Describe it in a sentence. Loopcut reads the scene, writes the bpy, runs it, and checks the viewport. Anything it gets wrong is one click back.
Scene hygiene
- Rename by material or hierarchy
- Sort into collections
- Purge orphans, apply scale, fix normals
Rigging plumbing
- Constraints and drivers
- Bone naming and symmetry
- Shape key setups
Geometry chores
- Modifier stacks in the right order
- UV seams and packing passes
- Retopology cleanup and merging
Look dev and output
- Light rigs and camera framing
- Render, colour and output presets
- Batch renders and exports
Learn while it works
Every step is readable Python. That is on purpose.
Loopcut does not hide what it does behind a button. The bpy it writes is the same bpy you would write, shown before it runs. Plenty of people have learned scripting by watching it, then taking over. That is a good outcome for us.
Free to start
Use your own key or a local model for nothing, forever. Or try the hosted free tier and keep going if it earns its place.
Open the file you have been avoiding.
Ask for the boring part. See the code. Keep the result, or don't.