Formatting Styles

Wispli offers 14 formatting styles to transform your speech into the perfect format for any context.

Overview

Style	Category	Best For
Raw	General	Debugging, exact transcription
Minimal	General	Quick notes, casual text
Clean & Correct	General	Professional content
Concise	General	Summaries, brief messages
Formal Report	Work	Business reports
Meeting Minutes	Work	Meeting notes
Professional Email	Email	Business emails
Friendly Reply	Email	Casual emails
Slack Message	Email	Chat messages
Git Commit	Developer	Version control
Bug Report	Developer	Issue tracking
Documentation	Developer	Technical docs
LinkedIn/Twitter	Social	Social media posts
Storytelling	Social	Narrative content

Style Details

Raw

Outputs exactly what was transcribed with no modifications.

Use when: Debugging, legal transcription, exact quotes

Input: "um so I think we should uh probably fix this bug"
Output: "um so I think we should uh probably fix this bug"

---

Minimal (Default)

Preserves your exact wording with basic cleanup.

Applied:

• Grammar and punctuation fixes
• Filler removal (um, uh, like)
• Repetition removal
• List detection

Not applied:

• Paraphrasing
• Tone changes

Input: "I have um three things first fix the bug second update docs third deploy"
Output: "I have three things:
1. Fix the bug
2. Update docs
3. Deploy"

---

Clean & Correct

Light smoothing for clarity while preserving meaning.

Applied:

• Everything in Minimal
• Sentence flow improvements
• Minor paraphrasing when needed

Input: "the thing is we need to like make sure the code works before we ship it"
Output: "We need to make sure the code works before we ship it."

---

Concise

Shortens text while preserving meaning.

Input: "I wanted to reach out to let you know that I think we should probably consider maybe pushing back the deadline a bit"
Output: "I think we should push back the deadline."

---

Formal Report

Professional report formatting with structure.

Input: "so basically sales went up twenty percent and we got three new clients"

Output:
"Summary

Sales performance increased by 20% during the reporting period. Additionally, three new clients were acquired."

---

Meeting Minutes

Structured meeting notes with clear sections.

Input: "we discussed the new feature John will handle the backend Sarah takes frontend deadline is next Friday"

Output:
"Meeting Minutes

Discussion Points:
• New feature implementation

Action Items:
• John: Handle backend development
• Sarah: Frontend implementation

Deadline: Friday"

---

Professional Email

Business email with greeting and closing.

Input: "hey can you send me the report by end of day thanks"

Output:
"Hi,

Could you please send me the report by end of day?

Thank you.

Best regards"

---

Friendly Reply

Warm, casual but professional tone.

Input: "got it will do thanks for letting me know"

Output:
"Got it! I'll take care of that.

Thanks for letting me know!"

---

Slack Message

Casual chat-style formatting.

Input: "the deployment is done everything looks good"

Output:
"deployment is done ✓
everything looks good 👍"

---

Git Commit

Conventional commit format.

Input: "fixed the login bug where users couldn't reset their password"

Output:
"fix(auth): resolve password reset issue

Users were unable to reset their password due to validation error.
Fixed the validation logic to properly handle reset tokens."

---

Bug Report

Structured bug report format.

Input: "the app crashes when you click the submit button on the contact form"

Output:
"## Summary
Application crashes on contact form submission.

## Steps to Reproduce
1. Navigate to contact form
2. Fill in form fields
3. Click submit button

## Expected Result
Form submits successfully.

## Actual Result
Application crashes."

---

Documentation

Technical documentation with markdown.

Input: "to install run npm install then create a config file and add your API key"

Output:
"## Installation

1. Install dependencies:
   \`\`\`bash
   npm install
   \`\`\`

2. Create a configuration file

3. Add your API key to the config"

---

LinkedIn/Twitter

Engaging social media format.

Input: "just launched our new feature that helps developers write code faster"

Output:
"🚀 Just launched our new feature!

Helping developers write code faster than ever.

#developer #productivity #coding"

---

Storytelling

Narrative flow with descriptive language.

Input: "we had a problem the server went down but the team fixed it quickly"

Output:
"We faced a challenge when the server went down unexpectedly. But our team rose to the occasion, working quickly to resolve the issue and restore service."

Global Rules

These rules apply to ALL styles (except Raw):

Always Applied

• ✅ Grammar and punctuation fixes
• ✅ Sentence capitalization
• ✅ Filler removal (um, uh, etc.)
• ✅ Accidental repetition removal
• ✅ Paragraph detection
• ✅ List/numbering detection

Never Applied

• ❌ Meaning changes
• ❌ Adding new ideas
• ❌ Removing important information
• ❌ Opinion injection

Switching Styles

During Recording

Press Tab to cycle through styles while recording.

In Settings

1. Open Settings → General
2. Select Default Style

Per-Session

Click the style dropdown in the main window before recording.

Next Steps

• Voice-to-Text - Transcription basics
• Custom Vocabulary - Add specialized terms
• For Developers - Developer-focused workflows