Saving a publication's design and settings as a reusable starting point for future content.
Definition
Save as Template is a feature that captures a publication's complete configuration — including [branding](/features/branding-and-design), viewer settings, [CTA buttons](/features/cta-buttons), [lead capture](/features/lead-capture) forms, and design choices — as a reusable starting point for future publications. Instead of rebuilding every setting from scratch each time you publish, you apply a saved template and only swap in the new PDF content. The template stores the functional and visual framework of a publication without retaining the actual document, so you can reuse the same setup across entirely different content.
Why It Matters
Consistency and speed are critical when publishing at scale. Manually reconfiguring branding colors, logos, lead forms, and viewer options for every new publication wastes time and introduces the risk of inconsistent experiences across your content library. A single mismatched color or missing lead form can undermine brand trust. Templates let teams maintain brand standards across dozens or hundreds of publications while cutting setup time from minutes to seconds. They also serve as a form of institutional knowledge: when a team member who set up the original configuration leaves, the template preserves their work for everyone who follows.
How It Works in FlipLink
FlipLink's [Save as Template](/features/save-as-template) feature stores all publication settings in a reusable template. After configuring a flipbook with your preferred branding, background music, CTA buttons, [password protection](/features/password-protection), or any other options, you save it as a template with a descriptive name. When creating a new flipbook or document, you select that template and all settings are pre-applied instantly. You can maintain multiple templates for different brands, campaigns, or document types. Templates work alongside [Duplicate Publication](/features/duplicate-publication) but are designed for applying settings across entirely new content rather than copying an existing publication.
When to Use It
Templates are most valuable in three scenarios. First, when you publish recurring content on a schedule — monthly newsletters, quarterly reports, weekly catalogs — and every edition needs identical branding and functionality. Second, when you manage publications for multiple brands or clients and need to switch between distinct configurations quickly. Third, when onboarding new team members who need to publish without memorizing the correct settings for each brand. If you only publish one-off flipbooks with unique settings each time, templates add less value. But the moment you find yourself configuring the same options twice, creating a template pays for itself.
Real-World Scenario
A real estate agency publishes property brochures as FlipLink flipbooks. Each office location has its own branding: different logo, contact details, and CTA linking to the local office's booking page. The marketing team creates one template per office — "Downtown Office," "Waterfront Office," "Suburban Office" — each with the correct logo, color palette, lead capture form, and CTA configuration. When a new listing arrives, the agent selects the matching office template, uploads the property PDF, and publishes in under two minutes. Without templates, each brochure would require manual configuration of eight or more settings, and a rushed agent might accidentally use the wrong office's branding.
Best Practices
**Name templates descriptively.** Use names like "Client X — Monthly Newsletter" or "Product Catalog — Enterprise" rather than "Template 1" or "New Template." Clear names prevent the wrong template from being applied, especially when multiple team members publish independently.
**Review templates periodically.** Branding evolves, CTA destinations change, and lead capture requirements shift over time. Set a quarterly reminder to open each template, verify that links and settings are still current, and update anything that has drifted.
**Keep templates focused.** Rather than creating one mega-template that tries to cover every use case, build separate templates for distinct publication types. A newsletter template and a product catalog template will serve you better than a single "general" template with settings that only half-apply to any given publication.
**Combine with Duplicate Publication when appropriate.** If you need to reuse both the settings and the content of an existing publication, [Duplicate Publication](/features/duplicate-publication) copies everything. Templates are the right choice when the content is new but the configuration should match a previous publication.