Branded presentation templates: PowerPoint and Keynote
Theme, template, and master slides are not synonyms
Confusion begins with terminology, and this is not a minor issue — it determines what exactly you are asking of a designer or contractor. A theme is a set of colors, fonts, and effects applied to a slide. A template (.potx or .key) is a file that not only preserves the theme but also ready-made layouts, field sizes, placeholder placement, and protected objects. Master slides are a mechanism within the template: a main slide plus child layouts through which all changes to the corporate style are transmitted to the entire document with one action.
If you manually edit the logo only on the title slide — you are working with a theme. If you change it on a master slide and it automatically updates on all 30 layouts — you are correctly working with a template.
PowerPoint versus Keynote: where compatibility breaks down
PowerPoint uses the 'Slide Master' mode (View → Slide Master) — there is one main slide and a set of child layouts bound to it hierarchically. Keynote is organized differently: 'Slide Layouts' exist more independently, without such a strict inheritance hierarchy. Because of this, conversion between formats almost never proceeds perfectly.
| Parameter | PowerPoint (.potx) | Keynote (.key) |
|---|---|---|
| Layout mechanism | Slide Master + child layouts | Slide Layouts (more flexible, less hierarchical) |
| Exporting to another format | Opens in Keynote with distortions | Exports to .pptx, but loses fonts, animations, and precise positioning |
| Font embedding | The 'Embed fonts in file' option when saving | Fonts are stored inside the .key package, but do not guarantee compatibility when exporting |
| Recommendation for the team | Separate .potx version | Separate .key version |
The takeaway is simple, and it's not about 'choosing one platform': if a company really works on both Windows and Mac, you need to maintain two parallel versions of the template — .potx and .key — with identical grids and colors, rather than relying on auto-conversion.
Fonts: why everything looks different on someone else's computer
The most common reason why a branded presentation 'spreads out' when opened by a client is the absence of the required font on their machine. PowerPoint quietly replaces the corporate font with a system font in this case, and all typography goes awry. The one-step solution: when saving the template, choose the .potx format (not the outdated .pot) and definitely enable the 'Embed fonts in file' option in the save settings. In Keynote, fonts are automatically packed into the file, but the problem returns when exporting to .pptx — font embedding is not guaranteed there, so final verification should be done on a clean machine without installed corporate fonts.
How many layouts are needed and how to protect the logo on the master slide
Template developers often overdo it: they make 60 layouts 'for all occasions' — and half of them are never used. Practice from brandbooks of large companies shows a different figure: 30-39 ready slides cover almost all real tasks of the team.
- Title slide — 2 variants (light and dark background)
- Text with a heading
- Text with an image
- Text in 2 columns
- Section divider
- Final slide / contacts
- Image gallery
- Infographics
- Tables and charts
This set of 9 typical categories, multiplied by light and dark themes and a couple of layout variations, gives those very 30+ slides.
A separate issue is the protection of critical elements. Let's take a real case: an agency delivers a template to a client, and a month later a marketer accidentally shifts the logo on the title slide to the left by one pixel when adding text, and six months later nobody remembers how it should look 'correctly.' The solution is to place the logo, the palette (usually 3-4 corporate colors), and the typographic pair (heading font + text font) not on individual slides, but on a master slide, grouped into a single object. Grouping prevents accidentally selecting and deleting one element separately from the others, and placing them specifically on the master guarantees that the logo will appear on all child layouts automatically. The optimal logo size is 5-10% of the slide height, a fixed angle (usually top left or bottom right), and PNG format with a transparent background — this excludes white underlays on colored slides.
Component library and when a third-party service is needed
A good template is not only slide layouts, but also a set of reusable modules: icons in a unified style, chart templates, and formatted tables. These should be stored as a separate block of slides within the template file itself (a 'library' that is copied and pasted), rather than in a separate PDF that nobody opens.
Built-in PowerPoint and Keynote tools are sufficient for 80% of companies. But if designs are created in Figma and the team needs to quickly turn finished layouts into working .potx files without manual reassembly — that's when services like OnBrandSlide or Twistly are brought in, which generate templates from uploaded designs. Canva Teams addresses a different task — collaborative work on presentations without deep customization of master slides, making it more of a content tool rather than a strict brand architecture instrument.
Template version control in the company
Here begins what instructions 'how to press the button' usually remain silent about. The template that was uploaded to the shared disk and forgotten is becoming obsolete faster than it seems: rebranding of color, a new slogan, font change — and three different versions of presentations spread throughout the office at the same time. Working practice — version files in the name (for example, Template_v3.2_2024) and keep a single source of truth in the cloud storage with restricted rights to edit master slides. Updating the template should be accompanied by a short newsletter with a list of changes, and old versions — archive, not delete, so as not to lose the history of decisions. For teams of 50+ people, it makes sense to appoint one 'template owner' — usually a brand manager or designer who unilaterally approves changes on the master slide and ensures that .potx and .key versions do not diverge from each other.
Theme, template, and master slides are not synonyms
Confusion begins with terminology, and this is not a minor issue — it determines what exactly you are asking of a designer or contractor. A theme is a set of colors, fonts, and effects applied to a slide. A template (.potx or .key) is a file that not only preserves the theme but also ready-made layouts, field sizes, placeholder placement, and protected objects. Master slides are a mechanism within the template: a main slide plus child layouts through which all changes to the corporate style are transmitted to the entire document with one action.
If you manually edit the logo only on the title slide — you are working with a theme. If you change it on a master slide and it automatically updates on all 30 layouts — you are correctly working with a template.
PowerPoint versus Keynote: where compatibility breaks down
PowerPoint uses the 'Slide Master' mode (View → Slide Master) — there is one main slide and a set of child layouts bound to it hierarchically. Keynote is organized differently: 'Slide Layouts' exist more independently, without such a strict inheritance hierarchy. Because of this, conversion between formats almost never proceeds perfectly.
| Parameter | PowerPoint (.potx) | Keynote (.key) |
|---|---|---|
| Layout mechanism | Slide Master + child layouts | Slide Layouts (more flexible, less hierarchical) |
| Exporting to another format | Opens in Keynote with distortions | Exports to .pptx, but loses fonts, animations, and precise positioning |
| Font embedding | The 'Embed fonts in file' option when saving | Fonts are stored inside the .key package, but do not guarantee compatibility when exporting |
| Recommendation for the team | Separate .potx version | Separate .key version |
The takeaway is simple, and it's not about 'choosing one platform': if a company really works on both Windows and Mac, you need to maintain two parallel versions of the template — .potx and .key — with identical grids and colors, rather than relying on auto-conversion.
Fonts: why everything looks different on someone else's computer
The most common reason why a branded presentation 'spreads out' when opened by a client is the absence of the required font on their machine. PowerPoint quietly replaces the corporate font with a system font in this case, and all typography goes awry. The one-step solution: when saving the template, choose the .potx format (not the outdated .pot) and definitely enable the 'Embed fonts in file' option in the save settings. In Keynote, fonts are automatically packed into the file, but the problem returns when exporting to .pptx — font embedding is not guaranteed there, so final verification should be done on a clean machine without installed corporate fonts.
How many layouts are needed and how to protect the logo on the master slide
Template developers often overdo it: they make 60 layouts 'for all occasions' — and half of them are never used. Practice from brandbooks of large companies shows a different figure: 30-39 ready slides cover almost all real tasks of the team.
- Title slide — 2 variants (light and dark background)
- Text with a heading
- Text with an image
- Text in 2 columns
- Section divider
- Final slide / contacts
- Image gallery
- Infographics
- Tables and charts
This set of 9 typical categories, multiplied by light and dark themes and a couple of layout variations, gives those very 30+ slides.
A separate issue is the protection of critical elements. Let's take a real case: an agency delivers a template to a client, and a month later a marketer accidentally shifts the logo on the title slide to the left by one pixel when adding text, and six months later nobody remembers how it should look 'correctly.' The solution is to place the logo, the palette (usually 3-4 corporate colors), and the typographic pair (heading font + text font) not on individual slides, but on a master slide, grouped into a single object. Grouping prevents accidentally selecting and deleting one element separately from the others, and placing them specifically on the master guarantees that the logo will appear on all child layouts automatically. The optimal logo size is 5-10% of the slide height, a fixed angle (usually top left or bottom right), and PNG format with a transparent background — this excludes white underlays on colored slides.
Component library and when a third-party service is needed
A good template is not only slide layouts, but also a set of reusable modules: icons in a unified style, chart templates, and formatted tables. These should be stored as a separate block of slides within the template file itself (a 'library' that is copied and pasted), rather than in a separate PDF that nobody opens.
Built-in PowerPoint and Keynote tools are sufficient for 80% of companies. But if designs are created in Figma and the team needs to quickly turn finished layouts into working .potx files without manual reassembly — that's when services like OnBrandSlide or Twistly are brought in, which generate templates from uploaded designs. Canva Teams addresses a different task — collaborative work on presentations without deep customization of master slides, making it more of a content tool rather than a strict brand architecture instrument.
Template version control in the company
Here begins what instructions 'how to press the button' usually remain silent about. The template that was uploaded to the shared disk and forgotten is becoming obsolete faster than it seems: rebranding of color, a new slogan, font change — and three different versions of presentations spread throughout the office at the same time. Working practice — version files in the name (for example, Template_v3.2_2024) and keep a single source of truth in the cloud storage with restricted rights to edit master slides. Updating the template should be accompanied by a short newsletter with a list of changes, and old versions — archive, not delete, so as not to lose the history of decisions. For teams of 50+ people, it makes sense to appoint one 'template owner' — usually a brand manager or designer who unilaterally approves changes on the master slide and ensures that .potx and .key versions do not diverge from each other.
Recent articles
MegaFon, BMW, VTB and more 240+ companies. See how it looks in the showcase reel:
Our branding agency is approached to order:
Branding agency services
