{"id":160,"date":"2026-07-20T14:20:45","date_gmt":"2026-07-20T14:20:45","guid":{"rendered":"https:\/\/99tools.net\/blog\/?p=160"},"modified":"2026-07-20T14:22:38","modified_gmt":"2026-07-20T14:22:38","slug":"how-to-convert-plain-text-to-markdown","status":"publish","type":"post","link":"https:\/\/99tools.net\/blog\/how-to-convert-plain-text-to-markdown\/","title":{"rendered":"How to Convert Plain Text to Markdown (3 Methods)"},"content":{"rendered":"\n<p class=\"wp-block-paragraph\">If you&#8217;ve ever pasted plain text into a README, a blog CMS, or a note-taking app and watched it come out as one giant, unformatted wall of text, you already know the problem. Plain text has no structure \u2014 no bold, no bullet points, no headings, just words and line breaks. Markdown fixes that with a handful of simple symbols that GitHub, static site generators, and most modern writing tools all understand.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">This guide covers three practical ways to convert plain text into clean Markdown: doing it by hand, using an online converter tool, and using a command-line tool for larger documents. You&#8217;ll learn when each method makes sense, the syntax you actually need to know, and the mistakes that trip up most beginners.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">What Markdown Actually Is (and Why It&#8217;s Worth Learning)<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Markdown is a lightweight markup language. Instead of clicking buttons in a word processor to make text bold or turn a paragraph into a list, you type a few characters around the text itself. An asterisk on each side makes something <em>italic<\/em>. Two asterisks make it <strong>bold<\/strong>. A pound sign at the start of a line turns it into a heading.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">The appeal is speed and portability. A <code>.md<\/code> file is still just plain text \u2014 you can open it in Notepad, VS Code, or any editor with zero special software. But the moment that file is viewed on GitHub, GitLab, a documentation site, or a blogging platform like Ghost or Hugo, those symbols get converted into properly styled HTML: real headings, real bold text, real lists.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">This is why Markdown has become the default format for:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>README files on GitHub and GitLab<\/li>\n\n\n\n<li>Technical documentation and knowledge bases<\/li>\n\n\n\n<li>Blog posts on platforms like Jekyll, Hugo, and Ghost<\/li>\n\n\n\n<li>Notes in apps like Obsidian and Notion<\/li>\n\n\n\n<li>Messages in tools like Slack and Discord (which use a simplified version)<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">If you write for the web or for developers, you&#8217;ll run into Markdown sooner or later. Converting plain text into it is really just &#8220;tagging&#8221; your content the way you&#8217;d naturally organize it \u2014 headings for sections, bullets for lists, bold for emphasis.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Before picking a method, it helps to read through your plain text once and mentally mark it up: what&#8217;s the title, what&#8217;s a list, what needs emphasis, is there a quote or a code snippet buried in there? That five-minute read-through saves you from converting line by line without a clear structure in mind \u2014 one of the most common reasons hand-converted Markdown ends up messy.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Method 1: Convert Plain Text to Markdown by Hand<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Hand-converting is the best way to actually learn Markdown, and it&#8217;s fast enough for anything under a page or two. Here&#8217;s the core syntax you need.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Headings<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Plain text usually shows a heading through capitalization or a blank line before it. In Markdown, use a pound sign (<code>#<\/code>) instead. The number of pound signs sets the heading level:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code># Main Title (Heading 1)\n## Section Heading (Heading 2)\n### Subsection Heading (Heading 3)\n<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Use only one <code>#<\/code> per document \u2014 that&#8217;s your title. Everything else should nest under <code>##<\/code> and <code>###<\/code>. Skipping levels (going from <code>#<\/code> straight to <code>###<\/code>) confuses both readers and screen readers, since heading levels double as a navigation structure for accessibility tools.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Bold and Italic<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">If your plain text uses ALL CAPS or underlines to show importance, replace that with Markdown emphasis:<\/p>\n\n\n\n<figure class=\"wp-block-table\"><table class=\"has-fixed-layout\"><thead><tr><th>Plain text style<\/th><th>Markdown syntax<\/th><th>Result<\/th><\/tr><\/thead><tbody><tr><td>Bold word<\/td><td><code>**word**<\/code><\/td><td><strong>word<\/strong><\/td><\/tr><tr><td>Italic word<\/td><td><code>*word*<\/code><\/td><td><em>word<\/em><\/td><\/tr><tr><td>Bold and italic<\/td><td><code>***word***<\/code><\/td><td><em><strong>word<\/strong><\/em><\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n<p class=\"wp-block-paragraph\">Pick either asterisks or underscores and stick with one style throughout the document. Mixing <code>_word_<\/code> and <code>*word*<\/code> isn&#8217;t technically wrong, but it makes the raw file harder to scan later.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Lists<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">This is where plain text often falls apart. A sentence like:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>To get started, install Node, then install the CLI, then run the init command.\n<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">&#8230;becomes a numbered list once you recognize it as sequential steps:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>1. Install Node\n2. Install the CLI\n3. Run the init command\n<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">For non-sequential items, use a hyphen followed by a space:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>- Fast setup\n- Works offline\n- No account required\n<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">For nested lists, indent consistently \u2014 two or four spaces, not a mix of both:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>- Frontend\n  - React\n  - Vue\n- Backend\n  - Node.js\n  - Django\n<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Inconsistent indentation is one of the most common reasons a nested list renders flat or oddly spaced. If that happens to you, check your indentation first before assuming something else is wrong.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Links, Images, Quotes, and Code<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Wrap raw URLs so readers see clean text instead of a long link:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>&#91;Markdown Guide's basic syntax reference](https:\/\/www.markdownguide.org\/basic-syntax\/)\n<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">For images, add an exclamation point in front, and always include real alt text \u2014 it&#8217;s shown if the image fails to load and read aloud by screen readers:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>!&#91;Screenshot of the dashboard](images\/dashboard.png)\n<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">For quoted passages, prefix each line with <code>&gt;<\/code>. For inline code, wrap it in backticks, like <code>`npm install`<\/code>. For multi-line code, use three backticks before and after, ideally with the language specified for syntax highlighting:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>```python\ndef greet(name):\n    print(f\"Hello, {name}\")\n```\n<\/code><\/pre>\n\n\n\n<h3 class=\"wp-block-heading\">Tables<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Tables are the trickiest thing to convert by hand, especially from a plain text source that used tabs or spaces to line things up (like a spreadsheet export). Markdown tables use pipes and a separator row:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>| Feature | Free Plan | Pro Plan |\n|---|---|---|\n| Storage | 5GB | 100GB |\n| Support | Email | Priority |\n<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">If you&#8217;re converting anything with more than three or four columns, or a lot of rows, doing it by hand gets tedious fast \u2014 misaligned pipes are easy to introduce and hard to spot. This guide on <a href=\"https:\/\/99tools.net\/blog\/how-to-create-tables-in-markdown\/\">how to create tables in Markdown<\/a> walks through column alignment, generating tables from CSV data, and handling tricky cases like empty cells, which is worth a read before you tackle anything beyond a small table.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Best for:<\/strong> short documents, single paragraphs, quick notes, or anytime you want to actually learn the syntax rather than just get output.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Method 2: Use an Online Text-to-Markdown Converter<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">For longer documents, or when you just need clean Markdown fast without typing every symbol yourself, an online converter does the heavy lifting. You paste in your plain text, and the tool detects likely structure \u2014 headings, lists, paragraphs \u2014 and outputs formatted Markdown.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">A tool like the <a href=\"https:\/\/99tools.net\/text-to-markdown-converter\/\">text-to-Markdown converter at 99Tools<\/a> is useful for this exact situation: you have a block of plain text (meeting notes, a draft, an exported document) and you want a Markdown-ready starting point in seconds instead of formatting every line by hand.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">That said, treat automated output as a first draft, not a final one. Converters make reasonable guesses, but they can&#8217;t always tell the difference between a line that&#8217;s meant to be a heading and one that&#8217;s just short. A quick pass to fix heading levels, tighten up list formatting, and double-check tables will save you from publishing something that looks almost right but not quite.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Best for:<\/strong> longer plain text documents, notes, or drafts where retyping every line manually isn&#8217;t worth the time \u2014 as long as you review the output before publishing.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Method 3: Convert Plain Text to Markdown with Pandoc<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">If you&#8217;re regularly converting documents \u2014 especially from other formats like <code>.docx<\/code> or <code>.html<\/code> into Markdown \u2014 a command-line tool is worth the setup time. <a href=\"https:\/\/pandoc.org\/\" target=\"_blank\" rel=\"noopener\">Pandoc<\/a> is the standard for this and handles structure detection more reliably than most online tools, particularly for longer files.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Once installed, a basic conversion looks like this:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>pandoc input.txt -f markdown -t markdown -o output.md\n<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">For converting a Word document into Markdown, which is a common real-world case for technical writers migrating old documentation:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>pandoc input.docx -o output.md\n<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Pandoc reads structural cues from the source formatting \u2014 headings styled in Word, existing bullet points, table structures \u2014 and maps them to the correct Markdown syntax automatically. This is where it has a real edge over both manual conversion and most web-based tools: it understands document structure, not just plain text patterns.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">The tradeoff is that Pandoc has a learning curve if you&#8217;ve never used a command-line tool before, and it&#8217;s overkill for a single short note. It earns its place when you&#8217;re converting documentation at scale, migrating a wiki, or regularly pulling content from other formats into Markdown.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Best for:<\/strong> batch conversions, migrating documentation, or converting from other file formats (Word, HTML) into Markdown.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Bonus: Automating in Bulk<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">If you&#8217;ve got an entire folder of <code>.txt<\/code> files to convert, you don&#8217;t want to run Pandoc on each one by hand. Loop through the directory and call Pandoc on every match instead. On Windows, PowerShell handles this in a few lines:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>Get-ChildItem -Path \"C:\\your-folder-path\" -Filter *.txt | ForEach-Object {\n    pandoc $_.FullName -f markdown -t markdown -o ($_.FullName -replace '\\.txt$', '.md')\n}\n<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">This runs Pandoc&#8217;s actual conversion on every <code>.txt<\/code> file in the folder and writes a matching <code>.md<\/code> file next to it \u2014 the original files are left untouched. On macOS or Linux, the bash equivalent is:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>for file in \/your-folder-path\/*.txt; do\n  pandoc \"$file\" -f markdown -t markdown -o \"${file%.txt}.md\"\ndone\n<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">One thing worth flagging here: simply renaming a <code>.txt<\/code> file&#8217;s extension to <code>.md<\/code> doesn&#8217;t convert anything. The content inside is untouched \u2014 no headings, no bold, no lists \u2014 so it still renders as plain paragraphs wherever it&#8217;s viewed. Running it through Pandoc, as both scripts above do, is what actually applies Markdown structure to the file.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Common Mistakes to Avoid (Regardless of Method)<\/h2>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Skipping heading levels.<\/strong> Jumping from <code>#<\/code> to <code>###<\/code> breaks the document outline.<\/li>\n\n\n\n<li><strong>Inconsistent list markers.<\/strong> Mixing <code>-<\/code>, <code>*<\/code>, and <code>+<\/code> in the same list works in most parsers but makes the file harder to maintain.<\/li>\n\n\n\n<li><strong>Forgetting blank lines around block elements.<\/strong> Lists, code blocks, and tables often need a blank line before and after them to render correctly \u2014 this causes a huge share of &#8220;why isn&#8217;t this formatting right&#8221; problems.<\/li>\n\n\n\n<li><strong>Not specifying a language on code blocks.<\/strong> Without it, you lose syntax highlighting for no real benefit.<\/li>\n\n\n\n<li><strong>Overusing bold text.<\/strong> If everything is bold, nothing stands out. Save it for genuinely important terms or warnings.<\/li>\n\n\n\n<li><strong>Trusting automated conversion blindly.<\/strong> Whether it&#8217;s an online tool or Pandoc, always preview the result before publishing.<\/li>\n\n\n\n<li><strong>Assuming every Markdown flavor behaves identically.<\/strong> GitHub, GitLab, and various blog platforms each support slightly different extensions, like task lists or strikethrough. Test on the platform where the file will actually be published.<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">That last point matters a lot for anyone publishing to GitHub specifically. A file that looks perfect in your local editor can render very differently once it&#8217;s pushed \u2014 missing spacing, broken tables, or lists that collapse into a single paragraph. If that&#8217;s happened to you, this breakdown of <a href=\"https:\/\/99tools.net\/blog\/why-your-readme-looks-broken-on-github\/\">why your README looks broken on GitHub<\/a> covers the specific formatting quirks that cause it and how to fix each one.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">A Quick Before-and-After Example<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Here&#8217;s a short plain text note:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>Project Setup Notes\n\nRequirements: Node 18+, npm, git\n\nSteps to install:\n1. Clone the repo\n2. Run npm install\n3. Copy .env.example to .env\n4. Run npm run dev\n\nNote: the dev server runs on port 3000 by default.\n<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Converted to Markdown:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code># Project Setup Notes\n\n**Requirements:** Node 18+, npm, git\n\n## Steps to Install\n\n1. Clone the repo\n2. Run `npm install`\n3. Copy `.env.example` to `.env`\n4. Run `npm run dev`\n\n&gt; Note: the dev server runs on port 3000 by default.\n<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Notice what changed: the title became a real heading, the requirements got a bold label, the commands are now in code formatting so they&#8217;re visually distinct from the surrounding text, and the note became a blockquote instead of a sentence with &#8220;Note:&#8221; tacked on the front. The content is identical \u2014 only the structure is now explicit.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Verifying Your Markdown Renders Correctly<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Whichever method you use, don&#8217;t assume the output is right \u2014 check it.<\/p>\n\n\n\n<ol class=\"wp-block-list\">\n<li><strong>Use a live preview editor<\/strong>, like VS Code&#8217;s built-in Markdown preview, before publishing anywhere.<\/li>\n\n\n\n<li><strong>Check the raw file for stray whitespace.<\/strong> Trailing spaces and inconsistent indentation are invisible in most editors but change how the file renders.<\/li>\n\n\n\n<li><strong>Preview on the actual target platform.<\/strong> GitHub&#8217;s README preview, your CMS&#8217;s preview mode, or your static site generator&#8217;s local build can each interpret spacing and syntax slightly differently, as explained in GitHub&#8217;s own <a href=\"https:\/\/docs.github.com\/en\/get-started\/writing-on-github\/getting-started-with-writing-and-formatting-on-github\/basic-writing-and-formatting-syntax\" target=\"_blank\" rel=\"noopener\">guide to basic writing and formatting syntax<\/a>.<\/li>\n\n\n\n<li><strong>Read it as a first-time visitor would.<\/strong> Structure that made sense to you while writing might still need more headings or shorter paragraphs to be genuinely readable.<\/li>\n<\/ol>\n\n\n\n<h2 class=\"wp-block-heading\">Which Method Should You Actually Use?<\/h2>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>A single note or short document?<\/strong> Convert it by hand. It takes a few minutes and you&#8217;ll learn the syntax in the process.<\/li>\n\n\n\n<li><strong>A longer document you need formatted quickly?<\/strong> Use an online converter like the <a href=\"https:\/\/99tools.net\/text-to-markdown-converter\/\">99Tools text-to-Markdown converter<\/a> as a starting point, then review and clean up the output.<\/li>\n\n\n\n<li><strong>Regular conversions, batch jobs, or migrating from Word or HTML?<\/strong> Set up Pandoc once and let it handle the heavy lifting going forward.<\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\">Final Thoughts<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Converting plain text to Markdown isn&#8217;t about memorizing every possible symbol \u2014 it&#8217;s about recognizing the structure already in your writing and making that structure explicit. Headings for sections, lists for steps, bold for emphasis, code blocks for anything technical. Whether you type it by hand, run it through a converter, or automate it with Pandoc, the goal is the same: text that&#8217;s easy to read as plain text and renders cleanly everywhere it&#8217;s published.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Start with one document you already have. Pick the method that fits its size, and you&#8217;ll come away with both a properly formatted file and a much better handle on Markdown itself.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>If you&#8217;ve ever pasted plain text into a README, a blog CMS, or a note-taking app and watched it come out as one giant, unformatted wall of text, you already know the problem. Plain text has no structure \u2014 no bold, no bullet points, no headings, just words and line breaks. Markdown fixes that with [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":161,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"site-sidebar-layout":"default","site-content-layout":"","ast-site-content-layout":"default","site-content-style":"default","site-sidebar-style":"default","ast-global-header-display":"","ast-banner-title-visibility":"","ast-main-header-display":"","ast-hfb-above-header-display":"","ast-hfb-below-header-display":"","ast-hfb-mobile-header-display":"","site-post-title":"","ast-breadcrumbs-content":"","ast-featured-img":"","footer-sml-layout":"","ast-disable-related-posts":"","theme-transparent-header-meta":"","adv-header-id-meta":"","stick-header-meta":"","header-above-stick-meta":"","header-main-stick-meta":"","header-below-stick-meta":"","astra-migrate-meta-layouts":"default","ast-page-background-enabled":"default","ast-page-background-meta":{"desktop":{"background-color":"var(--ast-global-color-5)","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"tablet":{"background-color":"","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"mobile":{"background-color":"","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""}},"ast-content-background-meta":{"desktop":{"background-color":"var(--ast-global-color-4)","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"tablet":{"background-color":"var(--ast-global-color-4)","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"mobile":{"background-color":"var(--ast-global-color-4)","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""}},"footnotes":""},"categories":[1],"tags":[],"class_list":["post-160","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-blog"],"_links":{"self":[{"href":"https:\/\/99tools.net\/blog\/wp-json\/wp\/v2\/posts\/160","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/99tools.net\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/99tools.net\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/99tools.net\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/99tools.net\/blog\/wp-json\/wp\/v2\/comments?post=160"}],"version-history":[{"count":2,"href":"https:\/\/99tools.net\/blog\/wp-json\/wp\/v2\/posts\/160\/revisions"}],"predecessor-version":[{"id":164,"href":"https:\/\/99tools.net\/blog\/wp-json\/wp\/v2\/posts\/160\/revisions\/164"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/99tools.net\/blog\/wp-json\/wp\/v2\/media\/161"}],"wp:attachment":[{"href":"https:\/\/99tools.net\/blog\/wp-json\/wp\/v2\/media?parent=160"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/99tools.net\/blog\/wp-json\/wp\/v2\/categories?post=160"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/99tools.net\/blog\/wp-json\/wp\/v2\/tags?post=160"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}