ElevenCreative Adds Templates for Reusable AI Creative Workflows
ElevenLabs is introducing Templates in ElevenCreative, a feature that turns its node-based Flows into reusable creative workflows with defined inputs and outputs. The company presents the tool as a way to run repeatable production tasks — such as product shots, mockups, style transfers, character sheets, and thumbnail translation — without rebuilding the workflow each time. Users can run templates from a gallery or publish their own, choosing which variables others can edit, what asset is returned, and whether access is private, workspace-only, or public.
Templates turn a flow into a reusable creative interface
Templates inside ElevenCreative are reusable creative workflows: a user supplies an input, runs the template, and receives a finished asset. The feature packages repeatable production processes so they can be run again without rebuilding the underlying workflow.
The template gallery sits inside the ElevenCreative interface as its own tab, alongside Home, Studio, Voices, Flows, and Files. It includes pre-built options organized by category, with visible examples across image tools, product shots, mockups, business-card mockups, and app mockups. Template names shown include “Place art on t-shirt,” “Put product in realistic environment,” “Showcase your business card,” “App Mockup,” and “Create a product shot grid.”
Using a template is presented as a three-step process: choose a template, provide the required input, and click generate. In the product-shot example, a user opens “Put product on bold background,” uploads a product image of a silver high-heeled shoe, and generates an output image placing the shoe on a solid purple background. The stated point is repeatability: the same template can be run “as many times as you need,” with different inputs.
Build a workflow once and turn it into an interface other people can run.
Templates are tied directly to ElevenCreative’s node-based Flows. A template is not shown as a prompt alone; it is a packaged workflow with defined inputs and outputs. The interface includes connected nodes for media processing, with visible labels such as Image, Video Retalking v2, Video Fast, and Composition. In the template-building example, that node structure becomes the mechanism for deciding what future users will upload, what variables they will control, and which generated asset they will receive.
The example template translates thumbnails while preserving brand names
The custom-template example packages a recurring task: translating a YouTube thumbnail into another language “in the click of a button.” The builder starts from “New Template,” which opens the Flow builder, then uploads a YouTube thumbnail image.
The workflow connects that image to an Edit Image node, whose visible model label is “GPT Image 2.” Instead of writing a fixed edit prompt, the builder connects the Edit Image node’s text input to an LLM node shown as “Gemini 2.5 Flash.” The LLM’s job is to generate the prompt that will drive the image edit.
The variable is the target language. A Text node is added and filled with “French” for the example run. The LLM prompt then references that Text node, so the language can change whenever the template is reused. The visible instruction asks the LLM to “write a prompt that will translate the attached YouTube thumbnail” into the referenced text value, and it adds a constraint: never translate “ElevenLabs” or “ElevenCreative.”
That exception is not incidental. The builder explains that those names should never be translated on the thumbnails. The output reflects the rule: the generated thumbnail contains the French phrase “Voyage à travers le temps grâce à l’IA,” while “ElevenLabs” remains in English.
The useful product detail is the layering. The template is not merely swapping text on an image. One node creates the instruction for another node, the target language is exposed as a reusable variable, and a brand-preservation rule is built into the workflow.
Publishing means deciding what the user is allowed to touch
Turning a working Flow into a Template happens from the Flow editor by clicking “Create Template.” The creation panel asks the builder to choose which parts of the underlying workflow become template inputs. In the thumbnail example, two inputs are selected: the original YouTube thumbnail image and the language text node.
Those inputs are renamed for the eventual template interface. The image input becomes “Thumbnail,” and the text input becomes “Language.” That naming step converts an internal node graph into a simpler front-end form: a future user does not need to understand the Flow canvas, only what file and variable to provide.
The builder then chooses the template output: the final generated image from the Edit Image node. After that selection, the template moves to publishing.
The publish panel asks for a name, category, and access setting. The template is named “Translate YouTube thumbnails” and saved under “Image Tools.” Access can be limited to a specific workspace or opened to everyone; the example uses “Everyone.” The stated model is that users can build and share templates broadly, not only keep them as private presets.
This publishing step is central to how the feature works. ElevenCreative is not only offering a gallery of ready-made assets. It lets a user take a Flow they have already built, decide which variables are exposed, decide what counts as the finished asset, and publish that workflow as a reusable object.
The gallery is both a starting point and a distribution surface
Templates serve two roles. They are ready-made workflows supplied through a gallery, where users can browse options for product photography, mockups, image tools, and similar creative tasks. They are also a distribution format for custom Flows. The same system that lets a user run “Put product on bold background” can publish “Translate YouTube thumbnails.”
The source description broadens the gallery beyond the examples shown in the interface. It lists product photography, ad creative, character design, image utilities, and style transfers, with examples such as turning a product photo into a lifestyle scene, generating a character sheet from a single portrait, and swapping ad headlines across formats and sizes.
Templates also appear in the ElevenLabs mobile app. A smartphone mockup shows a Templates screen with “Featured” templates and visible entries including “Translate image” and “Translate image variables.” The final product detail is that templates created by a user are available in the ElevenLabs app, so the same workflow can be accessed outside the desktop editor.
The practical argument is about reducing repeated setup. A recurring creative operation can be encoded once as a Flow, then exposed as a template with named inputs, a selected output, a category, and access permissions.