sodcalculator

10 Tech How-To

Move Obsidian Vault to Google Docs Without Losing Markdown Formatting

Guide 10-58331 · Updated · Step by step

Moving an Obsidian vault to Google Docs usually ends in broken links, lost headings, and mangled tables. This guide shows you a reliable method to convert your Markdown files into Google Docs while preserving the structure and formatting, using a combination of a Markdown-to-HTML converter and Google Docs’ built-in HTML import. You will need your Obsidian vault accessible on your computer and a Google account.

What You’ll Need

  • Your Obsidian vault folder (local or synced)
  • A Google account (free)
  • A web browser (Chrome, Firefox, Safari, or Edge)
  • A Markdown-to-HTML converter tool (we’ll use a free online one, but any local tool works)

Step-by-Step

  1. Prepare your vault. If your vault uses wiki-links (e.g., [[Note Name]]), decide whether you want them to become plain text or clickable links. For plain text, you can leave them as-is; for clickable links, you’ll need to convert them to standard Markdown links first (see Tips).
  2. Open the Markdown file. Navigate to the note you want to convert and open it in any plain text editor (Notepad, TextEdit, VS Code). Copy the entire content.
  3. Convert Markdown to HTML. Go to an online Markdown-to-HTML converter (e.g., markdowntohtml.com or dillinger.io). Paste your Markdown into the left panel. The right panel will show the HTML output. Copy the HTML code.
  4. Create a new Google Doc. Go to docs.google.com and create a blank document.
  5. Open the HTML import. In the Google Doc, go to File > Open > Upload. Select the HTML file you saved in the previous step (or you can paste the HTML directly using the Insert > HTML option if you have the Google Docs HTML extension installed). If you don’t have the extension, the upload method is the most reliable.
  6. Upload the HTML file. Save the HTML code as a .html file on your computer (e.g., note.html). Then in Google Docs, go to File > Open, click the Upload tab, and select that HTML file. Google Docs will convert it to a native document, preserving headings, bold, italics, lists, and tables.
  7. Review and fix formatting. After the import, scroll through the document. Check that headings are properly styled (not just bold text), lists are indented, and tables look correct. Sometimes the import may lose certain elements like horizontal rules or code blocks – you may need to re-add them manually.
  8. Handle images. If your note contains images stored in your vault, they won’t be embedded automatically. You’ll need to re-insert them manually: Insert > Image > Upload from computer or Drive.
  9. Fix links. If you converted wiki-links to standard Markdown links, they will appear as plain text URLs. You can convert them to clickable links by selecting the text and pressing Ctrl+K (or Cmd+K on Mac) and pasting the URL.
  10. Repeat for other notes. Because there’s no batch import, you’ll need to repeat steps 2-9 for each note you want to move. To speed up, consider using a script or a tool like Pandoc if you’re comfortable with command line.

Common Mistakes

  • Copying Markdown directly into Google Docs. Pasting raw Markdown into a Google Doc will not convert it – it will appear as plain text with asterisks and hashes. You must go through the HTML step.
  • Forgetting to convert wiki-links. Obsidian’s [[Note]] links are not standard Markdown. If you don’t convert them, they’ll appear as literal text like [[Note]] in your Google Doc.
  • Using the wrong HTML converter. Some converters output HTML with inline styles that Google Docs may not fully respect. Stick to well-known converters that produce clean, semantic HTML.
  • Ignoring code blocks. Code blocks (triple backticks) often lose their monospace formatting during import. You may need to reapply the Courier New font or use the Format > Paragraph styles > Code option if available.

Tips

  • Use Pandoc for batch conversion. If you’re moving many notes, Pandoc can convert a whole folder of Markdown files to HTML, preserving most formatting. Then you can upload each HTML file to Google Docs.
  • Convert wiki-links to standard links. Before converting, you can use a find-and-replace in your text editor to change [[Note]] to [Note](Note.md) or to the actual URL if you have a published vault. This makes the links clickable after import.
  • Use the Google Docs HTML extension. There is a Chrome extension called “Google Docs HTML” that lets you paste HTML directly into a doc. It’s faster than uploading files.
  • Check for tables. Tables in Markdown usually convert well to HTML, but if they don’t render correctly, try using a converter that supports GFM (GitHub Flavored Markdown) tables.

Troubleshooting

  • Formatting is completely lost. If the imported document looks like plain text, you may have pasted the Markdown directly instead of the HTML. Go back and copy the HTML output from the converter, then upload that as a file.
  • Headings are not recognized. If headings appear as bold text but not as actual heading styles, you can manually select the text and apply the appropriate heading style from the toolbar (e.g., Heading 1, Heading 2).
  • Images are missing. As mentioned, images won’t transfer automatically. You’ll need to re-insert them. If you have many images, consider using a cloud storage service and inserting them via URL.
  • Links are broken. If your links were relative (e.g., Note.md), they won’t work in Google Docs. You’ll need to update them to absolute URLs or remove them.
  • Special characters are garbled. Ensure your Markdown file is saved in UTF-8 encoding. If you’re using a converter, check that it also outputs UTF-8.

Frequently Asked Questions

Can I import multiple notes at once?

Google Docs doesn’t support batch import. You must import each note separately. However, you can use Pandoc to convert all your Markdown files to HTML first, then upload them one by one – that still saves time.

Will my Obsidian tags be preserved?

Tags like #tag will appear as plain text. Google Docs doesn’t have a native tag system, so you’ll need to manually format them (e.g., as bold or colored text) or leave them as plain text.

What about embedded notes or transclusions?

Obsidian’s ![[Note]] embeds won’t be converted. You’ll need to manually copy the content of the embedded note into the document, or replace it with a link.

Can I use Google Docs’ built-in Markdown import?

Google Docs doesn’t have a native Markdown import. The only way is to convert to HTML first. There are third-party add-ons, but they often have limitations.

Will the formatting be 100% identical to Obsidian?

No. Google Docs has its own styling engine, so some nuances (like specific fonts or spacing) may differ. You’ll likely need to make minor adjustments after import.

Is there a way to keep the Obsidian vault as the source of truth?

You can, but it requires manual effort: import the note into Google Docs, make edits there, then copy the content back to Obsidian as Markdown. This isn’t a seamless sync, so it’s better to decide on one primary platform.

Related

General steps for current mainstream versions; menus can differ by device and version. See the disclaimer or report an error.

More in this bed

The whole Tech How-To bed →