# How to Record Audio on MacBook & MacBook Pro
**Related topics:** how to record audio on a Mac, how to record system audio on Mac, how to record computer audio on Mac, how to record with audio on Mac
If you only need to record your own voice on a Mac, the built-in apps are usually enough. If you also want to capture audio from a video, a browser tab, or another app, you will need one extra step because macOS does not treat system sound as a standard recording source. This guide covers both cases, so you can choose the simplest method for what you actually need.
## Quick comparison: which app should you use?
| App | Best for | Install | System audio |
| ----------------------------- | ------------------------------------------------------ | ------------- | ----------------------------- |
| **Voice Memos** | Fast voice notes and casual recordings | Built-in | No |
| **QuickTime Player** | Simple microphone recording with a little more control | Built-in | No (yes with a virtual input) |
| **GarageBand** | Podcasts, music, and multi-track projects | Built-in | No (requires extra routing) |
| **BlackHole + recording app** | Capturing audio played by your Mac | Extra install | Yes |
## The easiest ways to record audio on Mac
The best method depends on what you are trying to capture. For spoken notes, meetings, or rough voice-over takes, start with the built-in tools. For internal audio, such as music or video playback, you will need a virtual audio device.
### Record your voice quickly with Voice Memos
**Voice Memos** is the fastest option if you want to record speech without adjusting many settings. It opens quickly, saves automatically, and works well for short notes, interviews, and basic drafts.
**How to use Voice Memos:**
- Open **Applications** and launch **Voice Memos**.
- Click the red **Record** button.
- Speak into your Mac’s built-in microphone or an external mic.
- Click **Stop** when you are finished.
- Rename the recording if needed.
If speed matters more than advanced controls, this is the most convenient built-in recorder on Mac.
Optional shortcut from Terminal:
```bash
open -a "Voice Memos"
```
### Use QuickTime Player for simple, clean recordings
**QuickTime Player** is a better choice when you want a straightforward audio file and the ability to pick a microphone manually. It is still simple, but gives you a bit more control than Voice Memos.
**How to record audio in QuickTime:**
- Open **QuickTime Player**.
- Choose **File** → **New Audio Recording**.
- Click the arrow next to the record button to choose your microphone.
- Click **Record** to start.
- Click **Stop** when you are done.
- Save the file to your preferred location.
QuickTime is a good middle ground for users who want something cleaner than Voice Memos without moving into a full editing app.
```bash
open -a "QuickTime Player"
```
## How to record system audio on Mac
If you want to record sound coming from your Mac itself, such as a YouTube video, a meeting playback, or in-app audio, the built-in tools alone are not enough. macOS does not expose system audio as a default recording input.
To capture internal audio, most users install a virtual audio device such as **BlackHole** or **Soundflower**. Once installed, that virtual device appears as an available input inside apps like QuickTime, OBS, or other recording software.
**Basic workflow:**
- Install a virtual audio driver such as **BlackHole**.
- Open **Audio MIDI Setup**.
- Configure your output and monitoring as needed.
- Select the virtual device as the input in your recording app.
- Play the audio you want to capture and start recording.
If you need to hear the sound while recording it, you will usually create a **Multi-Output Device** in Audio MIDI Setup so the audio can go to both your speakers or headphones and the virtual input.
If you use [Homebrew](https://brew.sh){rel=""nofollow""}, you can check what BlackHole package names are currently available:
```bash
brew search blackhole
brew update
# brew info blackhole-2ch
# brew install blackhole-2ch
open -a "Audio MIDI Setup"
```
## When to use GarageBand
**GarageBand** makes sense when you need more than a one-click recording tool. It is better suited to podcasts, music demos, layered voice work, and any project where you may want to trim, mix, or arrange multiple tracks.
**How to record in GarageBand:**
- Open **GarageBand** and start a new project.
- Create or select an audio track.
- Choose the correct input source.
- Click **Record**.
- Edit, trim, or mix the track after recording.
- Export the final file when ready.
For quick one-off voice notes, GarageBand is more than you need. For repeat content production, it is often worth the extra setup.
```bash
open -a "GarageBand"
```
## Tips for better recording quality
Even the right app will not fix a noisy room or a poor mic position. A few small adjustments can improve clarity right away.
### Good starting input levels
| Source | Suggested peak level | Notes |
| ------------------- | ------------------------------ | --------------------------------------------------- |
| Speaking voice | −12 dBFS to −6 dBFS | Leaves headroom for louder moments |
| Acoustic instrument | −18 dBFS to −12 dBFS | Move the mic before over-boosting gain |
| System or app audio | Match the app output carefully | Watch for clipping if multiple sources are combined |
**Quick quality tips:**
- Record in a quiet room whenever possible.
- Use an external microphone if you want cleaner voice recordings.
- Keep input gain high enough for clarity, but low enough to avoid distortion.
- Make a short test recording before anything important.
- Use headphones if you need to monitor sound without speaker bleed.
If you want to inspect audio devices from the Terminal, macOS includes a simple system report:
```bash
system_profiler SPAudioDataType | head -n 80
system_profiler SPAudioDataType | rg -i "microphone|input|blackhole" || true
```
## Common reasons people record audio on Mac
- Saving voice notes or spoken ideas
- Recording podcasts or voice-overs
- Capturing online lessons or meeting playback where permitted
- Saving app or browser audio for editing or review
- Creating short audio clips for content publishing
## Conclusion
For most Mac users, **Voice Memos** and **QuickTime Player** are the easiest ways to record voice audio. If you need to record internal sound, add a virtual audio device such as **BlackHole** and route it through your recording app. Once you know which tool matches your use case, recording audio on a Mac becomes much simpler.
# 在 MacBook 与 MacBook Pro 上轻松录制音讯
**相关主题：** 如何在 Mac 上录音讯、如何录制 Mac 系统音讯、如何录制电脑播放音讯、如何搭配音讯录制
如果你只是想在 Mac 上录下自己的声音，其实用内建工具就够了；如果你还想把影片、浏览器分页或 App 播放出来的声音一起录下来，就需要多做一步设定。這篇會把兩種情況分開講清楚，讓你可以直接找到最適合自己的做法。
## 快速比較：該用哪一個 App？
| App | 適合情境 | 是否需另外安裝 | 能否直接錄系統聲 |
| ---------------------- | --------------- | ------- | ----------- |
| **語音備忘錄** | 快速語音、臨時記錄、簡單訪談 | 內建 | 否 |
| **QuickTime Player** | 簡單錄音、可選麥克風、操作直覺 | 內建 | 否（搭配虛擬輸入可行） |
| **GarageBand** | Podcast、音樂、多軌錄製 | 內建 | 否（需額外路由） |
| **BlackHole + 錄音 App** | 錄下 Mac 正在播放的聲音 | 需額外安裝 | 是 |
## 在 Mac 上錄音，最常用的幾種方法
先決定你要錄的是什麼。如果只是錄人聲、口述筆記或簡單旁白，內建工具通常就很夠用；如果你要錄的是電腦本身播放的聲音，例如影片、課程或網頁音訊，就要另外加入虛擬音訊裝置。
### 用「語音備忘錄」快速錄下人聲
**語音備忘錄**是最省事的做法。開啟就能錄，幾乎不用調整設定，特別適合臨時記錄想法、語音筆記，或先快速錄一段草稿。
**使用步驟：**
- 打開 **「應用程式」**，啟動 **「語音備忘錄」**。
- 點一下紅色 **「錄音」** 按鈕。
- 對著 Mac 內建麥克風，或外接麥克風開始說話。
- 錄完後按 **「停止」**。
- 視需要重新命名錄音檔。
如果你最在意的是方便和速度，語音備忘錄通常就是最直接的選擇。
選用：也可以從終端機直接開啟：
```bash
open -a "Voice Memos"
```
### 用 QuickTime Player 做更乾淨的基礎錄音
如果你想手動選擇麥克風，或希望輸出一個更容易整理的音訊檔，**QuickTime Player** 會比語音備忘錄更合適。它不複雜，但比前者多一點控制空間。
**使用步驟：**
- 開啟 **QuickTime Player**。
- 在上方選單選 **「檔案」** → **「新增音訊錄製」**。
- 點開錄音按鈕旁的選單，選擇要使用的麥克風。
- 按 **「錄製」** 開始。
- 完成後按 **「停止」**。
- 將檔案存到你要的位置。
如果你想要比語音備忘錄更穩定一點、但又不想直接進到專業剪輯工具，QuickTime 是很實用的折衷方案。
```bash
open -a "QuickTime Player"
```
## 如何錄製 Mac 的系統音訊
如果你要錄的是 Mac 本身播放出來的聲音，例如 YouTube、線上課程、會議回放或其他 App 音效，光靠內建工具通常不夠。原因是 macOS 不會直接把系統音訊當成預設錄音輸入來源。
這種情況下，多數人會安裝像 **BlackHole** 或 **Soundflower** 這類虛擬音訊裝置。安裝完成後，它會出現在 QuickTime、OBS 或其他錄音軟體的輸入清單中，讓你把系統播放的聲音導入錄音流程。
**基本流程如下：**
- 安裝虛擬音訊驅動，例如 **BlackHole**。
- 開啟 **「音訊 MIDI 設定」**。
- 依需求設定輸出與監聽方式。
- 在錄音 App 中，把輸入來源切換成虛擬音訊裝置。
- 播放你要錄下的聲音，然後開始錄音。
如果你希望錄音的同時自己也能聽到聲音，通常還需要在 **「音訊 MIDI 設定」** 裡建立 **多重輸出裝置（Multi-Output Device）**，把聲音同時送到耳機或喇叭，以及虛擬輸入端。
如果你有使用 [Homebrew](https://brew.sh){rel=""nofollow""}，可以先查目前有哪些可用的 BlackHole 套件名稱：
```bash
brew search blackhole
brew update
# brew info blackhole-2ch
# brew install blackhole-2ch
open -a "Audio MIDI Setup"
```
## 什麼情況下適合用 GarageBand？
如果你不只是想錄一段聲音，而是還想剪輯、混音、安排多軌，**GarageBand** 就會比前面兩個工具更適合。它比較像是製作型工具，適合 Podcast、音樂 Demo、旁白專案或固定產出的內容流程。
**使用步驟：**
- 開啟 **GarageBand** 並建立新專案。
- 新增或選取一個音訊軌道。
- 設定正確的輸入來源。
- 按下 **「錄音」** 開始。
- 錄完後進行剪輯、修整或混音。
- 最後輸出成你需要的格式。
如果你只是偶爾錄個語音，GarageBand 可能有點太重；但如果你經常做內容，這類工具就很值得熟悉。
```bash
open -a "GarageBand"
```
## 讓錄音品質更好的幾個重點
就算選對了 App，環境太吵、麥克風位置不對，錄出來的效果還是會打折。很多時候，只要調整幾個小地方，聲音就會明顯乾淨很多。
### 輸入音量可先參考這個範圍
| 來源 | 建議峰值區間 | 備註 |
| ---------- | ------------------- | ---------------- |
| 口語人聲 | −12 dBFS 到 −6 dBFS | 保留一點空間，避免突然大聲時失真 |
| 原聲樂器 | −18 dBFS 到 −12 dBFS | 先調整距離，再考慮提高增益 |
| 系統或 App 音訊 | 依輸出音量微調 | 多來源混在一起時要特別留意爆音 |
**幾個實用做法：**
- 盡量在安靜的空間錄音。
- 想提升人聲品質時，優先考慮外接麥克風。
- 輸入音量不要太低，也不要高到失真。
- 正式開始前，先試錄一小段。
- 需要監聽時，盡量用耳機避免喇叭回授。
如果你想用終端機快速查看 Mac 的音訊裝置資訊，也可以用系統內建指令：
```bash
system_profiler SPAudioDataType | head -n 80
system_profiler SPAudioDataType | rg -i "microphone|input|blackhole" || true
```
## 常見的 Mac 錄音情境
- 記錄語音筆記或臨時想法
- 錄製 Podcast、旁白或口述內容
- 在允許的前提下保存線上課程或會議回放
- 錄下瀏覽器、影片或 App 的播放聲音
- 製作短音訊素材，用於內容發布
## 結論
對大多數使用者來說，**語音備忘錄** 和 **QuickTime Player** 已經足夠應付日常錄音需求。如果你要錄的是 Mac 正在播放的聲音，再加上像 **BlackHole** 這樣的虛擬音訊裝置就可以處理。先釐清自己要錄的是人聲還是系統音訊，選工具就會簡單很多。
# Changelog
# Core Features
# FAQ
# Channel Connection
# View all integrations
Browse supported services and connection steps. Pick a chat provider below for step-by-step setup.
# 7-Day Learning Path
# Full Markdown Example
# Headers
```text
# h1 Heading 8-)
## h2 Heading
### h3 Heading
#### h4 Heading
##### h5 Heading
###### h6 Heading
Alternatively, for H1 and H2, an underline-ish style:
Alt-H1
======
Alt-H2
------
```
# h1 Heading 8-)
## h2 Heading
### h3 Heading
#### h4 Heading
##### h5 Heading
###### h6 Heading
Alternatively, for H1 and H2, an underline-ish style:
# Alt-H1
## Alt-H2
---
# Emphasis
```text
Emphasis, aka italics, with *asterisks* or _underscores_.
Strong emphasis, aka bold, with **asterisks** or __underscores__.
Combined emphasis with **asterisks and _underscores_**.
Strikethrough uses two tildes. ~~Scratch this.~~
**This is bold text**
__This is bold text__
*This is italic text*
_This is italic text_
~~Strikethrough~~
```
Emphasis, aka italics, with *asterisks* or *underscores*.
Strong emphasis, aka bold, with **asterisks** or **underscores**.
Combined emphasis with **asterisks and *underscores***.
Strikethrough uses two tildes. ~~Scratch this.~~
**This is bold text**
**This is bold text**
*This is italic text*
*This is italic text*
~~Strikethrough~~
---
# Lists
```text
1. First ordered list item
2. Another item
⋅⋅* Unordered sub-list.
1. Actual numbers don't matter, just that it's a number
⋅⋅1. Ordered sub-list
4. And another item.
⋅⋅⋅You can have properly indented paragraphs within list items. Notice the blank line above, and the leading spaces (at least one, but we'll use three here to also align the raw Markdown).
⋅⋅⋅To have a line break without a paragraph, you will need to use two trailing spaces.⋅⋅
⋅⋅⋅Note that this line is separate, but within the same paragraph.⋅⋅
⋅⋅⋅(This is contrary to the typical GFM line break behaviour, where trailing spaces are not required.)
* Unordered list can use asterisks
- Or minuses
+ Or pluses
1. Make my changes
1. Fix bug
2. Improve formatting
- Make the headings bigger
2. Push my commits to GitHub
3. Open a pull request
* Describe my changes
* Mention all the members of my team
* Ask for feedback
+ Create a list by starting a line with `+`, `-`, or `*`
+ Sub-lists are made by indenting 2 spaces:
- Marker character change forces new list start:
* Ac tristique libero volutpat at
+ Facilisis in pretium nisl aliquet
- Nulla volutpat aliquam velit
+ Very easy!
```
1. First ordered list item
2. Another item
⋅⋅\* Unordered sub-list.
3. Actual numbers don't matter, just that it's a number
⋅⋅1. Ordered sub-list
4. And another item.
⋅⋅⋅You can have properly indented paragraphs within list items. Notice the blank line above, and the leading spaces (at least one, but we'll use three here to also align the raw Markdown).
⋅⋅⋅To have a line break without a paragraph, you will need to use two trailing spaces.⋅⋅
⋅⋅⋅Note that this line is separate, but within the same paragraph.⋅⋅
⋅⋅⋅(This is contrary to the typical GFM line break behaviour, where trailing spaces are not required.)
- Unordered list can use asterisks
- Or minuses
- Or pluses
1. Make my changes
1. Fix bug
2. Improve formatting
- Make the headings bigger
2. Push my commits to GitHub
3. Open a pull request
- Describe my changes
- Mention all the members of my team
- Ask for feedback
- Create a list by starting a line with `+`, `-`, or `*`
- Sub-lists are made by indenting 2 spaces:
- Marker character change forces new list start:
- Ac tristique libero volutpat at
* Facilisis in pretium nisl aliquet
- Nulla volutpat aliquam velit
- Very easy!
---
# Task lists
```text
- [x] Finish my changes
- [ ] Push my commits to GitHub
- [ ] Open a pull request
- [x] @mentions, #refs, [links](), **formatting**, and tags supported
- [x] list syntax required (any unordered or ordered list supported)
- [x] this is a complete item
- [ ] this is an incomplete item
```
- Finish my changes
- Push my commits to GitHub
- Open a pull request
- @mentions, #refs, [links](), **formatting**, and ~~tags~~ supported
- list syntax required (any unordered or ordered list supported)
- this is a complete item
- this is an incomplete item
---
# Ignoring Markdown formatting
You can tell GitHub to ignore (or escape) Markdown formatting by using \ before the Markdown character.
```text
Let's rename \*our-new-project\* to \*our-old-project\*.
```
Let's rename \*our-new-project\* to \*our-old-project\*.
---
# Links
```text
[I'm an inline-style link](https://www.google.com)
[I'm an inline-style link with title](https://www.google.com "Google's Homepage")
[I'm a reference-style link][Arbitrary case-insensitive reference text]
[I'm a relative reference to a repository file](../blob/master/LICENSE)
[You can use numbers for reference-style link definitions][1]
Or leave it empty and use the [link text itself].
URLs and URLs in angle brackets will automatically get turned into links.
http://www.example.com or and sometimes
example.com (but not on Github, for example).
Some text to show that the reference links can follow later.
[arbitrary case-insensitive reference text]: https://www.mozilla.org
[1]: http://slashdot.org
[link text itself]: http://www.reddit.com
```
[I'm an inline-style link](https://www.google.com){rel=""nofollow""}
[I'm an inline-style link with title](https://www.google.com "Google's Homepage"){rel=""nofollow""}
[I'm a reference-style link](https://www.mozilla.org){rel=""nofollow""}
[I'm a relative reference to a repository file](https://zenai.bot/../blob/master/LICENSE)
[You can use numbers for reference-style link definitions](http://slashdot.org){rel=""nofollow""}
Or leave it empty and use the [link text itself].
URLs and URLs in angle brackets will automatically get turned into links.
{rel=""nofollow""} or {rel=""nofollow""} and sometimes
example.com (but not on Github, for example).
Some text to show that the reference links can follow later.
---
# Images
```text
Here's our logo (hover to see the title text):
Inline-style:
Reference-style:
![alt text][logo]
[logo]: https://github.com/adam-p/markdown-here/raw/master/src/common/images/icon48.png "Logo Title Text 2"
Like links, Images also have a footnote style syntax
![Alt text][id]
With a reference later in the document defining the URL location:
[id]: https://octodex.github.com/images/dojocat.jpg "The Dojocat"
```
Here's our logo (hover to see the title text):
Inline-style:
Reference-style:
Like links, Images also have a footnote style syntax
With a reference later in the document defining the URL location:
---
# [Footnotes](https://github.com/markdown-it/markdown-it-footnote){rel=""nofollow""}
```text
Footnote 1 link[^first].
Footnote 2 link[^second].
Inline footnote^[Text of inline footnote] definition.
Duplicated footnote reference[^second].
[^first]: Footnote **can have markup**
and multiple paragraphs.
[^second]: Footnote text.
```
Footnote 1 link[1](https://zenai.bot/#user-content-fn-first){#user-content-fnref-first ariaDescribedBy=""footnote-label"" dataFootnoteRef=""}.
Footnote 2 link[2](https://zenai.bot/#user-content-fn-second){#user-content-fnref-second ariaDescribedBy=""footnote-label"" dataFootnoteRef=""}.
Inline footnote^ [Text of inline footnote] definition.
Duplicated footnote reference[2](https://zenai.bot/#user-content-fn-second){#user-content-fnref-second-2 ariaDescribedBy=""footnote-label"" dataFootnoteRef=""}.
---
# Code and Syntax Highlighting
```text
Inline `code` has `back-ticks around` it.
```
Inline `code` has `back-ticks around` it.
```c#
using System.IO.Compression;
#pragma warning disable 414, 3021
namespace MyApplication
{
[Obsolete("...")]
class Program : IInterface
{
public static List JustDoIt(int count)
{
Console.WriteLine($"Hello {Name}!");
return new List(new int[] { 1, 2, 3 })
}
}
}
```
```css
@font-face {
font-family: Chunkfive;
src: url("Chunkfive.otf");
}
body,
.usertext {
color: #f0f0f0;
background: #600;
font-family: Chunkfive, sans;
}
@import url(print.css);
@media print {
a[href^="http"]::after {
content: attr(href);
}
}
```
```javascript
function $initHighlight(block, cls) {
try {
if (cls.search(/\bno\-highlight\b/) != -1)
return process(block, true, 0x0F) +
` class="${cls}"`;
} catch (e) {
/* handle exception */
}
for (var i = 0 / 2; i < classes.length; i++) {
if (checkCondition(classes[i]) === undefined)
console.log('undefined');
}
}
export $initHighlight;
```
```php
require_once 'Zend/Uri/Http.php';
namespace Location\Web;
interface Factory
{
static function _factory();
}
abstract class URI extends BaseURI implements Factory
{
abstract function test();
public static $st1 = 1;
const ME = "Yo";
var $list = NULL;
private $var;
/**
* Returns a URI
*
* @return URI
*/
static public function _factory($stats = array(), $uri = 'http')
{
echo __METHOD__;
$uri = explode(':', $uri, 0b10);
$schemeSpecific = isset($uri[1]) ? $uri[1] : '';
$desc = 'Multi
line description';
// Security check
if (!ctype_alnum($scheme)) {
throw new Zend_Uri_Exception('Illegal scheme');
}
$this->var = 0 - self::$st;
$this->list = list(Array("1"=> 2, 2=>self::ME, 3 => \Location\Web\URI::class));
return [
'uri' => $uri,
'value' => null,
];
}
}
echo URI::ME . URI::$st1;
__halt_compiler () ; datahere
datahere
datahere */
datahere
```
---
# Tables
```text
Colons can be used to align columns.
| Tables | Are | Cool |
| ------------- |:-------------:| -----:|
| col 3 is | right-aligned | $1600 |
| col 2 is | centered | $12 |
| zebra stripes | are neat | $1 |
There must be at least 3 dashes separating each header cell.
The outer pipes (|) are optional, and you don't need to make the
raw Markdown line up prettily. You can also use inline Markdown.
Markdown | Less | Pretty
--- | --- | ---
*Still* | `renders` | **nicely**
1 | 2 | 3
| First Header | Second Header |
| ------------- | ------------- |
| Content Cell | Content Cell |
| Content Cell | Content Cell |
| Command | Description |
| --- | --- |
| git status | List all new or modified files |
| git diff | Show file differences that haven't been staged |
| Command | Description |
| --- | --- |
| `git status` | List all *new or modified* files |
| `git diff` | Show file differences that **haven't been** staged |
| Left-aligned | Center-aligned | Right-aligned |
| :--- | :---: | ---: |
| git status | git status | git status |
| git diff | git diff | git diff |
| Name | Character |
| --- | --- |
| Backtick | ` |
| Pipe | \| |
```
Colons can be used to align columns.
| Tables | Are | Cool |
| ------------- | :-----------: | ----: |
| col 3 is | right-aligned | $1600 |
| col 2 is | centered | $12 |
| zebra stripes | are neat | $1 |
There must be at least 3 dashes separating each header cell.
The outer pipes (|) are optional, and you don't need to make the
raw Markdown line up prettily. You can also use inline Markdown.
| Markdown | Less | Pretty |
| -------- | --------- | ---------- |
| *Still* | `renders` | **nicely** |
| 1 | 2 | 3 |
| First Header | Second Header |
| ------------ | ------------- |
| Content Cell | Content Cell |
| Content Cell | Content Cell |
| Command | Description |
| ---------- | ---------------------------------------------- |
| git status | List all new or modified files |
| git diff | Show file differences that haven't been staged |
| Command | Description |
| ------------ | -------------------------------------------------- |
| `git status` | List all *new or modified* files |
| `git diff` | Show file differences that **haven't been** staged |
| Left-aligned | Center-aligned | Right-aligned |
| :----------- | :------------: | ------------: |
| git status | git status | git status |
| git diff | git diff | git diff |
| Name | Character |
| -------- | --------- |
| Backtick | \` |
| Pipe | \| |
---
# Blockquotes
```text
> Blockquotes are very handy in email to emulate reply text.
> This line is part of the same quote.
Quote break.
> This is a very long line that will still be quoted properly when it wraps. Oh boy let's keep writing to make sure this is long enough to actually wrap for everyone. Oh, you can *put* **Markdown** into a blockquote.
> Blockquotes can also be nested...
>> ...by using additional greater-than signs right next to each other...
> > > ...or with spaces between arrows.
```
> Blockquotes are very handy in email to emulate reply text.
> This line is part of the same quote.
Quote break.
> This is a very long line that will still be quoted properly when it wraps. Oh boy let's keep writing to make sure this is long enough to actually wrap for everyone. Oh, you can *put* **Markdown** into a blockquote.
> Blockquotes can also be nested...
>
> > ...by using additional greater-than signs right next to each other...
> >
> > > ...or with spaces between arrows.
---
# Inline HTML
```text
- Definition list
- Is something people use sometimes.
- Markdown in HTML
- Does *not* work **very** well. Use HTML tags.
```
- - Definition list
- Is something people use sometimes.
- Markdown in HTML
- Does \*not\* work \*\*very\*\* well. Use HTML *tags*.
---
# Horizontal Rules
```text
Three or more...
---
Hyphens
***
Asterisks
___
Underscores
```
Three or more...
---
Hyphens
---
Asterisks
---
Underscores
---
# YouTube Videos
```text
```
[{border="10" height="180" width="240"}](http://www.youtube.com/watch?feature=player_embedded&v=YOUTUBE_VIDEO_ID_HERE)
```text
[](http://www.youtube.com/watch?v=YOUTUBE_VIDEO_ID_HERE)
```
[](https://www.youtube.com/watch?v=ciawICBvQoE){rel=""nofollow""}
## Footnotes
1. Footnote **can have markup**:br and multiple paragraphs. [↩](https://zenai.bot/#user-content-fnref-first){.data-footnote-backref ariaLabel="Back to reference 1" dataFootnoteBackref=""}
2. Footnote text. [↩](https://zenai.bot/#user-content-fnref-second){.data-footnote-backref ariaLabel="Back to reference 2" dataFootnoteBackref=""} [↩2](https://zenai.bot/#user-content-fnref-second-2){.data-footnote-backref ariaLabel="Back to reference 2-2" dataFootnoteBackref=""}
# ZenAion
ZenAion is a personal AI agent OS for turning conversations into automated workflows across messaging, files, research, scheduling, and other connected tools.
## Primary Pages
- Home: https://zenai.bot/
- Pricing: https://zenai.bot/pricing
- Guide: https://zenai.bot/guide
- Blog: https://zenai.bot/blog
- Contact: https://zenai.bot/contact
## Machine-readable Notes
- Public pages use canonical URLs without the default `/en` prefix.
- Localized URLs are listed only when a page has a real localized source.
- Private account, login, and admin pages are excluded from public indexing surfaces.