Life has been very good to web writers who prefer to plain text. Just in the last year, we’ve seen a number of great tools that make creating HTML from plain text (specifically, Markdown) easy peasy.

As prevalent as the web is, however, there are still lots (read: LOTS) of people who still have to ship their writing in love-it-or-hate-it Microsoft Word. Many publishers know nothing other than Word, and try as you might, they won’t change.

Whenever I write articles for newsletters and other publications, editors expect me to send my words in Word—even when the articles will ultimately be published online (in HTML). It’s a silly state of affairs, but it’s the world today.

As always, adaptation is better than inaction. Fortunately, there’s a relatively easy way to write in Markdown but ship in Word.

When it comes to writing, I think of Word as the internet. It’s a destination, not a vehicle.

I’ll show you how to get there, but only after I satisfy my compulsion to gush about Markdown.

Markdown monogamy

I’m at the point now where I can’t not write in gloriously naked plain text. In fact, it’s probably not a stretch to say that this site wouldn’t exist without Markdown. Seriously. When I discovered John Gruber’s Markdown (and Fletcher Penney’s MultiMarkdown variant), the volume of what I wrote exploded.

Virtually everything I’ve written in the last two years has its roots in plain text. And trust me, kids; it’s not some obsession with old school nerdery. Plain text is just infinitely more practical for at least three good reasons, which are enough for me.

First, it’s everywhere:

My life doesn’t allow me to sit in front of a full keyboard all day. But as long as my incubating ideas are in plain text, I can work on them any time life offers me the chance. That’s because I keep all of my drafts in Simplenote and Dropbox.

As long as I have an iOS device handy, I can proof and polish an article while I sit in the waiting room of a behind-schedule doctor’s office. I can jot down ideas as I read in a coffee shop. I can collect hyperlinks from my mobile RSS reader and put them directly into drafts. All without ever touching my Mac.

Try pulling off that mobile workflow in Word.

Second, it causes me to write:

I’ve said it before; I’ll say it again: Word is not a writing application. It’s a desktop publishing application. When I start a writing project of any size in Word, it feels like I’m starting to build a house by first worrying about wall colors.

With its ticker tape of attention-sabotaging features, Word constantly gives you a finish line illusion.

Words aren’t worthy of cosmetics until they say something. More importantly, each second you spend fiddling with the aesthetics of your document is a second spent not writing. Accumulated over just a few days, that can be a tremendous number of seconds.

Third, it’s practically invincible:

Plain text doesn’t die. Applications don’t drop support for plain text. Plain text is the most portable, the most searchable, the most light weight medium for your writing.

Okay, done gushing.

Going from Markdown to Word

You don’t hear people talk about it a lot, but it’s quite possible—and relatively straightforward after some moderate geeking around.

I’ll walk you through these main steps:

  1. Install MultiMarkdown
  2. Convert (Multi)Markdown to open document format (FODT)
  3. Save FODT as DOC

Step 1: Install MultiMarkdown

See Fletcher Penney’s site for more details on downloading and installation. Specifically, you’ll need, which is included in the main package.

I recommend putting your MultiMarkdown things in ~/Library/Application Support/MultiMarkdown/.

Step 2: Convert to FODT

I’m going to talk about two ways of using Fletcher’s script: 1) geekier 2) less geeky.


If you’re handy in Terminal, doing the conversion is easy. Just modify ~/.bash_profile so that it has this line:

export “PATH=/Users/[YOUR HOME FOLDER NAME]/Library/Application Support/MultiMarkdown/bin:$PATH”

And, of course, replace [YOUR HOME FOLDER NAME] with the name of your home folder.[1] After reloading .bash_profile, you should be able to simply type: yourmarkdownfile.txt

You’ll see yourmarkdownfile.fodt appear in the same folder.

Tip: create a short TextExpander snippet to expand for you.

Less geeky

Just so you have no excuses, I’ll give you service that does all that Terminal business for you as long as you have MultiMarkdown installed in ~/Library/Application Support/MultiMarkdown/ like I said above.


  1. Download and unzip it
  2. Copy ConvertToODF.workflow to ~/Library/Services
  3. Open ConvertToODF.workflow in Automator, and replace [YOUR HOME FOLDER NAME] with the name of your home folder.[2]
  4. Save your changes

Convert to odf pe

To use, simply select a Markdown file in Finder and run the service (Finder > Services). Out should pop a .fodt file.

I recommend creating a keyboard shortcut for this service if you’re going to use it a lot. Go to System Preferences > Keyboard > Keyboard Shortcuts, and look in the Services section.

Services shortcut pe

Step 3: Saving FODT as DOC

FODT is an open document format. The “F” is for flattened. Not important.

You can’t open FODT in Word, but you can open it in or LibreOffice. Both are free, and both allow you to save in a Word format (.doc).

LibreOffice opens FODT automatically, but requires an add-on. I followed Fletcher’s simple instructions for installing the add-on in, and it works great.

Just open FODT in either program and save it as DOC. Done.

Why this is worth your time

FODT preserves virtually all of the formatting you create in (Multi)Markdown. Things like italicized text, bold text, headings, and bulleted lists, appear as they should. That’s important because it minimizes the effort needed to polish the text at the finish line. In fact, you may not have to do anything at all.

Spending just a little time on the back end to convert Markdown to FODT then save FODT as DOC is a small price to pay for the efficiency you’re gaining during the plain text writing phase.

  1. H/t to Brett Terpstra for help on this.


  2. For example, if your home folder is called Sam, the path would be /Users/Sam/Library/…

    </li> </ol> </div>