MarkdownPad's only requirement is the Microsoft .NET Framework 4 Client Profile, which will be automatically installed if you don't already have it. MarkdownPad is compatible with Windows XP, Windows Vista, Windows 7, and Windows 8.
MarkdownPad is currently available in the following languages:
To change languages in MarkdownPad, navigate to Tools → Options → Interface tab and select a language under Application Language.
Yes! If you'd like to help translate MarkdownPad, please visit the MarkdownPad Translation Project.
MarkdownPad includes an automatic update feature which is powered by an open source tool called wyUpdate. This application must be present for MarkdownPad's automatic update feature to function properly.
Yes, although it is no longer officially supported. Click here to download the original version of MarkdownPad.
Yes, they are completely separate applications and can be installed side-by-side.
MarkdownPad is free for personal use, and you can upgrade to MarkdownPad Pro to unlock additional features and support the developer. You can also check out a full feature comparison between the Free and Pro versions.
For commercial use, please purchase a MarkdownPad Pro license.
MarkdownPad Pro is licensed via a Single User license. This means that the software license "follows" the end user, allowing them to use MarkdownPad Pro on multiple computers as long as the end-user is the only person using the license at any time.
If any other users will use the software, an additional Single User license must be obtained for each user.
Jim purchases one MarkdownPad Pro Single User license. He owns a laptop and a desktop computer. He can use the license on both computers, as long as he is the only person using the license.
Diane has 5 employees, and purchases one MarkdownPad Pro Single User license for one of her employees. If she wants all of her employees to use MarkdownPad Pro, she must purchase additional Single User licenses for each user - 5 total.
If you have any questions about licensing, please contact us and we'd be glad to help.
MarkdownPad Pro licenses can be purchased using either PayPal or Amazon Payments from the Buy MarkdownPad Pro page. If you have questions about payments or want to discuss alternate payment methods, please contact us.
Yes. Please contact us for more information.
Please contact email@example.com and we'll re-issue you the license immediately. Please include the email address you used to purchase the license (it should be your PayPal or Amazon Payments email address) and your transaction ID if possible.
An error occurred while processing the license keywhen I enter it into MarkdownPad.
This error can be caused if a Microsoft dependency is missing from your operating system. If you receive this error, please install the Microsoft Visual C++ 2010 SP1 Redistributable Package (x86).
A new MarkdownPad 2 installer was released on 2013-03-07 that will verify this dependency is installed on your system. If it isn't, the installer will offer to add it for you.
If you continue to have any issues activating your license, please contact us and we'd be glad to help.
PayPal users have the option of enabling an advanced security feature called PayPal Security Key, which is a form of two-factor authentication.
To use PayPal Security Key while purchasing a MarkdownPad Pro license, you must append your security key to the end of your PayPal password. For example, if you PayPal password was
markdown and your PayPal security key was
123456, you would enter
markdown123456 as your password while purchasing a license.
Spell check can be toggled under
Enable Spell Check.
Due to license restrictions for spell check dictionaries, MarkdownPad can only include a limited set of dictionaries. However, you can install new dictionaries following the instructions below.
.zipformat. If it is in a different format, change the file extension to
.zipfile and extract its contents.
.affand one that ends in
C:\Program Files\MarkdownPad 2\SpellCheck\dictionaries\
C:\Program Files (x86)\MarkdownPad 2\SpellCheck\dictionaries\
.dicfiles from Step 3 to the
dictionariesdirectory in Step 4.
.dicfiles are named using the standardized, official Culture Info name, with the language code separated from the culture code with an underscore (
F7) and locate the newly added language in the Spell Check Dictionaries list.
This process will be simplified in a future version of MarkdownPad.
MarkdownPad 2 was designed with a high-performance Markdown rendering engine. This allowed MarkdownPad 2 to handle documents of any size, even in situations where MarkdownPad 1 would begin to experience performance issues. However, this high-performance rendering engine had a few side effects that caused minor rendering issues in LivePreview with elements like complex nested lists, long code blocks, and reference-style hyperlinks and images.
With the release of MarkdownPad 2.1.13, you can now choose which rendering method is right for you: High Performance mode or Full Document mode. Full Document mode is enabled by default, but you can change the rendering mode under
Markdown tab →
Here's what you need to know about the two systems:
Full Document Mode
This mode is similar to the original rendering system used in MarkdownPad 1, and will render your entire document in the LivePreview pane. This means your documents will appear as intended in the LivePreview pane. The downsides are that this mode may experience performance issues in large documents (20,000+ words) and you may find that the scrollbar synchronization is less accurate than in High Performance mode.
High Performance Mode
This is the mode that originally launched with MarkdownPad 2. Along with other improvements, only the content that is visible in the Editor pane will be rendered in the LivePreview pane. This mode can handle documents of any length, and will typically offer more accurate scrollbar synchronization. Its downside is that you may observe some minor rendering issues in certain situations (although they only affect LivePreview, nothing else).
Named anchors allow you to click a link in a document and be taken to a different location within the same document.
Yes, this is possible. Markdown specification allows raw HTML to be used in a Markdown document, so we can use that functionality to insert named anchors.
To get started, you just need to insert some very simple HTML into your document wherever you want to define a destination. This HTML is called a "named anchor", and looks like this:
Add that code in front of whatever content you want to "jump" to, like so:
<a name="myAnchor"></a> ## My Header ## This is some content in my first section.
When your document is converted to HTML, you won't see the
<a name="..." part anymore, but now you can refer to its specific name from anywhere else in the document.
You can add a link to
myAnchor in your Markdown document like this:
[Go To Section One](#myAnchor)
Note: Make sure to prefix the link with the # symbol.
So to put it all together, a document with named anchors might look like this:
# Table of Contents - [Go to Section One](#sectionOne) - [Go to Section Two](#sectionTwo) <a name="sectionOne"></a> ## My First Header ## This is some content in my first section. <a name="sectionTwo"></a> ## My Second Header ## This is some content in my second section.
This technique is used to build the MarkdownPad FAQ page, which you're currently viewing.
Official support for external stylesheets is not yet available in MarkdownPad, although it will be added in a future update.
However, external stylesheets can be used right now with a simple procedure:
Addbutton to add a new stylesheet (or
Editto edit an existing stylesheet)
@import url("YOUR-CSS-URL");, replacing YOUR-CSS-URL with the path to your external CSS file
That's it! Please note that this will include a reference to the stylesheet in your document; the stylesheet itself will not be included locally.
This view has crashed!
This issue has been specifically observed in Windows 8. You may see an error message as shown here, and no HTML will be rendered when you type in the Markdown Editor pane.
To fix this issue, please install Microsoft's DirectX End-User Runtimes (June 2010).
If you continue to have issues, please try installing the Awesomium 1.6.6 SDK.
By default, MarkdownPad uses a
Full Document rendering mode. This mode can cause minor position synchronization issues in specific scenarios, especially when dealing with long documents that use HTML elements that have a larger vertical space footprint than their Markdown equivalents.
To fix this issue, try changing to
High Performance rendering mode under
Markdown tab →
Rendering Mode. Click here for more information.
IME is an text input system frequently used by Chinese and Japanese-speaking users.
This issue has been fixed as of MarkdownPad v2.1.6. Please update to the newest version of MarkdownPad when possible.
This issue was resolved in MarkdownPad v2.1.12.
If you are using Headings in the format of
#This is my heading (without a space between the
# symbol and the Heading text), they may not be rendered correctly in GitHub Flavored Markdown. This is due to an inconsistency of Markdown processing in the official GitHub API.
To resolve the issue, you can include a space between the
# symbol and the Heading text. For example,
# This is my heading would be properly rendered.