Sometimes you want to start from a solid, well-tested Template instead of building one from scratch. Today we’re announcing Builtin Templates: Transloadit-maintained, versioned Templates that you can reference by template_id like any other Template.

Builtin Templates are designed for common transformations and quick building blocks. They are stable, they are versioned, and you can pin to a specific version when you need a change-controlled deployment.

What are Builtin Templates

Builtin Templates live inside API2 and are identified by slugs that start with builtin/, for example:

  • builtin/encode-hls-video@0.0.1
  • builtin/serve-preview@0.0.1

You can use them via template_id:

  • builtin/<name> resolves to the latest known version.
  • builtin/<name>@latest is an explicit alias for the latest known version.
  • builtin/<name>@<version> pins to a specific version.

Why use them

  • Start from a known-good baseline for common transformations.
  • Keep your integration lean: no need to create a Template just to try something out.
  • Pin versions for predictable behavior, and upgrade when you’re ready.
  • Combine them with your own steps by overriding at runtime, like any other Template.

Quick example: create an Assembly using a Builtin Template

Here’s the shape of an Assembly request using a Builtin Template:

{
  "template_id": "builtin/encode-hls-video"
}

You can still override or extend steps at runtime (for example, to add a storage export step), the same way you would with any Template. For background on overriding, see Templates.

Explore what’s available

We keep the canonical list and usage notes in the docs:

If you want them to show up in API listings, you can include them in GET /templates with include_builtin (see the endpoint reference for details):

What’s next

Builtin Templates are a small surface today, and we’ll expand them based on real-world usage. If you have a transformation you run repeatedly and you think it belongs as a Builtin Template, let us know.

If you’re not using Templates yet, start there first: