Template Editor
Template Editor

How Brand Kits work: from kit to template to flick

The one-page mental model for how one Brand Kit flows to every template and every flick, what updates on its own, and why a finished video never changes.

A Brand Kit is your organization's branding, kept in one place and reused everywhere. Set it up once and it flows to every template your team builds and every flick they shoot from those templates, so the work stays on-brand without anyone rebuilding a watermark or endslate by hand. It still leaves each video maker room to make the video their own.

A kit holds only the pieces you want in it. It can be as small as a single watermark, or a full set: colors, logo, music, intro and outro clips, an endslate, caption and title styles, share tags, a template icon, and a default Author Credit. Anything a kit leaves out simply falls through to the video maker's own choice, so a kit never has to be "complete" to be useful. (Brand Kits come with Team plans and up.)

The three layers

Branding moves through three stages: the Brand Kit (the source your admins build), the template (a reusable recipe a member builds, with one kit applied), and the flick (the finished video an app user makes from that template).

Reading the diagram

  • Live: the kit's look updates automatically when an admin publishes.
  • Snapshot: a few fields refresh only on Re-apply or Auto-apply, and never overwrite your edits.
  • Pinned: a flick is frozen at a version; a finished video won't change under you.

Auto-apply never overwrites a customization: a customized template keeps its edits and shows the update banner instead.

While a flick is still in progress, an in-app prompt lets the video maker choose whether to adopt a newer version.

Updates travel forward, into templates and new flicks. They never reach back into videos already made.

From the Share screen, a video maker can render one flick in several Brand Kits at once, so the same shots are delivered in each brand's look.

Two things flow differently

When an admin publishes a new version of a kit, most of it, the look, reaches your templates on its own: colors, logo, watermark, endslate, the intro and outro clips, music, and caption and title styles are read live from the kit, so a template always shows the current version with nothing to re-apply.

A few fields work the other way. Share tags, the intro/outro wording, the Author Credit, and the template icon are copied onto a template when the kit is applied, so an author's own edits are never overwritten by a later kit change. Those refresh when the author re-applies, or, if the org turns it on, when auto-apply quietly refreshes the ones no one has customized. The template author guide has the full field-by-field breakdown.

Updates travel forward, not backward

Publishing a new version reaches your templates and any new flick made from them afterward. It never reaches back into videos already made: each flick is pinned to the kit version it was shot with, so a later change can't alter a finished or in-progress video out from under the video maker. If the kit changes while a flick is still in progress, the app offers the video maker the update, and taking it is their choice.

Who does what

Where these live

Brand Kits and templates live in the web dashboard: kits on the Brand Kits page, templates in the template editor. Flicks are made in the NanoFlick app. The kit is the single source; the dashboard is where you shape how it reaches everyone's work.

Last verified