The template library

The library is where finished templates are shared. Some are ours; the rest come from people using Puffin Ship who thought a pipeline they built was worth passing on. Everything in it has been read by a person before it appears.

What you see

The gallery in Build a Template has three groups:

Featured, a small set worth trying first.
Official, written and maintained by us.
Community, submitted by other users and reviewed before publication.

Every card tells you what matters before you commit: what the template does, who wrote it (unless they chose to publish anonymously), how many people have installed it, which service keys of your own it will need, and roughly what a run costs.

Installing is copying

Installing a template copies it into your workspace. From that moment it is yours: you can rename it, rewire it, delete steps, and run it. Nothing links back to the original.

That has two consequences worth knowing.

The author cannot reach into your copy. If they publish an improved version, your copy stays as it was, and you can install the new one alongside it if you want the changes.

And if the author later withdraws their template, your copy keeps working. Withdrawal stops distribution; it does not reach into workspaces.

What a shared template does and does not carry

A template carries its steps, their settings, and the prompts that drive them. It does not carry footage, and it does not carry keys.

Anything that needs an API key uses yours, from your workspace's Variables & Service API Keys. A template can name a key it needs; it can never contain one. The library refuses a submission that appears to have a key pasted into it.

File inputs come across as names. A template that expected a folder called broll will look for a folder called broll in your workspace, so the first thing to check after installing is that the inputs point at your files.

See Sharing a template for the walkthrough. In short: a workspace owner shares a template from the editor, it goes into a review queue, and it appears in the gallery once it has been approved and published. You keep ownership; you can withdraw it at any time.

Review

Every submission is read before it is published, not scanned. Automatic checks catch the careless mistakes (a template that does not parse, steps that do not fit together, a key pasted into a setting), but the things worth catching are the ones only a person notices: a prompt that says something it should not, a description that does not match what the template actually does, a step that exists only to spend the installer's credits.

A rejected submission comes back with a reason, and you can fix it and send it again.

Blocks