Overview: What Is Style Guide?
Style Guide is Jasper's content governance tool that lets workspace admins define precise rules for how AI-generated content should look, sound, and read — from comma usage and em-dashes to branded terminology and case sensitivity.
Jasper now applies style rules automatically at generation time, the same way Brand Voice, Audiences, and Knowledge work. You no longer need to manually apply suggestions after content is created. Style is woven in from the first draft, making output more consistent and reducing review cycles.
Style Guide is available on Business plans only.
How it Works
Style applied at generation time
Style rules are applied automatically when content is generated — in Chat, across Apps, and within Canvas inline editing tools. You get consistent, on-style output from the start, without manual post-processing.
Canvas now applies your active Style Guide in two additional places:
- Ask Jasper (highlight menu) — Highlight any text in a Canvas document and choose an edit from the Ask Jasper menu. The active Style Guide is now applied automatically, alongside Brand Voice and Audience.
- Slash Commands (/) — Type / in a Canvas document to open the popover ("Continue writing", "Add image"). Content generated here now inherits the active Style Guide as well.
Both changes are fully additive — Brand Voice and Audience inheritance continues to work exactly as before.
Style Guide and the Public API: Style Guide rules now apply to all string values in structured JSON responses returned by the Public API — including nested fields. Behavior is consistent whether content is generated through the UI or via API, across both structured and unstructured parts of the payload.
Multiple style guides per workspace
You can create and manage multiple style guides within a single workspace. This is ideal if your team manages multiple brands, content types, or follows different style systems (e.g. AP, MLA, or custom). Each guide can be tailored independently and switched depending on the task.
Default style guides at workspace and project level
Set a default style guide for your entire workspace, or configure a per-project default in Canvas — so the right guide is always active without requiring manual selection each time.
Selecting a Style Guide
You can choose a style guide anywhere you select Brand Voice, Audiences, or Knowledge: - Chat — Select a style guide from the IQ selector panel before generating. - Agent Settings — Configure a style guide in Custom or Studio Agent settings so all output from that agent follows the same rules automatically. - Project Settings (Canvas) — Set a default style guide per project, ideal for teams that work primarily within one style system for a given body of work. This style guide is automatically applied across all Canvas inline editing, including Ask Jasper and Slash Commands. - Workspace Settings — Set a workspace-level default that applies across all content generation.
Only one style guide can be active at a time, consistent with how Brand Voice and Audiences work.
Recently used: All IQ dropdowns — including Style Guide — now show a Recently used section at the top with your three most recently selected items. This makes it faster to get back to the Style Guides you use most, without scrolling through the full list. All other guides appear in an All section below.
Managing Multiple Style Guides
Navigate to Workspace Settings → Style Guides to: - Create multiple style guides - Rename, edit, and organize them - Set a workspace-level default - Control editing permissions — only Admins and Managers can create or edit style guides
Style Guide Rules
Oxford Comma
Jasper offers two clear options for Oxford comma behavior: - Use Oxford commas — Jasper adds a comma before "and" or "or" in a list of three or more items. (Example: apples, oranges, and bananas.) - Don't use Oxford commas — Jasper omits the comma before "and" or "or" in a list. (Example: apples, oranges and bananas.)
Both options send explicit instructions to the AI, so your preference is always honored.
AP Style note: If you use the AP Style Preset, Jasper automatically applies the correct AP Style exceptions for Oxford comma edge cases.
Migration: Existing style guides that previously had this feature disabled were automatically migrated to "Use Oxford commas," which matches default model behavior.
Em-Dash Rules
- Avoid em-dashes (—) toggle
- When ON (blue): Jasper avoids em-dashes in generated content, replacing them with a comma, period, semicolon, or colon — whichever is grammatically appropriate.
- When OFF (grey): Jasper does not restrict em-dashes.
Dynamic settings: If "Avoid em-dashes" is ON, the secondary "Use spaces before and after the em-dash" toggle is automatically hidden and treated as OFF to prevent conflicting rules.
Case Sensitivity
Jasper supports per-rule case sensitivity, giving you tighter control over branded terms, acronyms, and product names where capitalization carries meaning. - Case-sensitive matching ON: Jasper matches the target word or phrase only when capitalization matches exactly. (Example: A rule for "US" matches "US" but not "us.") - Case-sensitive matching OFF (default): Jasper matches the word or phrase regardless of capitalization.
The case sensitivity toggle defaults to OFF for new rules. All existing Style Guide rules have been automatically migrated to case-insensitive matching.
Hyphen Normalization
Style Guide rules now run against normalized text: Unicode hyphens and dash variants (such as the non-breaking hyphen) are automatically converted to standard ASCII hyphens before your rules are evaluated.
This means rules written with a regular hyphen — like a rule for "best-selling" — now correctly match content where the model outputs a Unicode hyphen variant. Rules are less likely to fail silently just because the separator character wasn't the standard ASCII hyphen.
Abbreviation Rules
Style Guide now recognizes and normalizes abbreviations across multiple input forms on their first occurrence in a piece of content. If you've defined an abbreviation rule — for example, mapping "Customer Relationship Management" to "CRM" — Jasper handles all of the following correctly:
- The full term: "Customer Relationship Management"
- The abbreviation alone: "CRM"
- The canonical form: "Customer Relationship Management (CRM)"
- The reverse form: "CRM (Customer Relationship Management)"
Whichever form appears first becomes the standardized version — collapsing to just "CRM" on all subsequent mentions.
Casing: Abbreviation matching is now strictly case-sensitive. The rule only matches the exact casing defined in your style guide. Advise your team to review existing abbreviation examples to make sure casing in their content matches what's in the guide.
Edge cases to keep in mind: - Single mentions still expand to the canonical form, even if the term is never used again - Standalone abbreviations expand on their first and only use - If the bare full term appears before the canonical form, the first mention uses the full term and later mentions collapse to the abbreviation
Grammar & Punctuation: Regional Customization Removed
The regional customization option in Grammar & Punctuation has been removed. This option conflicted with the Language setting in Canvas Project Settings. To produce localized output, use Project Settings → Language instead.
Availability
Style Guide is available on Business plans only. Creator and Pro plans do not have access to Style Guide.
Only workspace Admins and Managers can create and edit style guides. All users can select and apply them when generating content.
Frequently Asked Questions
Can I apply multiple style guides at once? No. One style guide can be active at a time, which is consistent with how Brand Voice and Audiences work.
Can permissions restrict who can edit or create style guides? Yes. Style guides follow the same Admins and Managers permissions structure as the rest of Jasper IQ.
What happened to regional customization in Grammar & Punctuation? It's been removed because it conflicted with Canvas Project Settings language configuration. Use Project Settings → Language for localized output.