# Settings: Processor

Options in the Marked Settings, Processor pane:

Settings: Processor

### Process Markdown with

Default Markdown processor. The Discount processor is preferred for GitHub users, MultiMarkdown is ideal for writers. Marked compensates for some differences between syntax. See Help->Markdown Reference for additional information.

Custom Rules
  Click the Custom Rules button to open the Rules Editor, where you can specify different processors and document transformations to run based on matching criteria. See Custom Processor for details.

To explore the differences between the processors, check out the Markdown Dingus.

### HTML

Generate IDs on headlines
  Generate header IDs based on contents of h1-h6 tag.

Use random footnote IDs
  Generate random footnote IDs to avoid conflicts when multiple documents are displayed on one page.

Process Markdown inside of HTML
  By default, Markdown inside of HTML tags is usually ignored. This option forces Marked to continue processing within block elements. Note that some markup may cause issues.

### Rendering

Retain line breaks in paragraphs
  Respect line breaks in paragraph text, replacing with hard breaks instead of concatenating with the previous line.

Render GitHub checkboxes
  Render `- [ ]` and `- [x]` for creating checkboxes in lists. Checkboxes are rendered for preview but not functional within Marked.

#Text is tag
  Allows hashtags, (`#` immediately followed by text with no space) to be interpreted as tags, not headlines. This functionality is default for Bear users.
  Style tags causes tags to be displayed with “capsule” formatting to distinguish them from text. When this is enabled, tags can be shown/hidden using ⚙ Proofing Show Comments.

#Text is tag enabled

Render `==highlight==` and `~~delete~~`
  If this option is enabled, then `==highlight==` text will be rendered as an HTML `<mark>` tag, which will appear as a yellow highlight unless otherwise modified by a Style. Additionally, `~~delete~~` syntax will be rendered with a `<del>` tag.
  If Render as CriticMarkup is enabled, then `==highlight==` and `~~delete~~` syntax will be converted to CriticMarkup, which can then be displayed in original, markup, and edited views.

Render `~text~` as underscore
  If this option is enabled, `~text~` surrounded by single tildes will be rendered as underlined. This conflicts with MultiMarkdown syntax for subscript and is disabled by default.

#### Next up: Settings: Apps ▶

Support Site | Knowledgebase