Skip to content

Need personal help? We reply quickly.

Reach our team directly — we walk new creators through setup.

InkToAudio help center

How to use InkToAudio

A complete, plain-English guide for turning your writing into studio-quality audio and distributing it as a podcast. Every feature is explained step by step — no technical knowledge required.

Add audio to your Ghost posts

Ghost is friendly to embeds: its HTML card runs custom scripts and iframes on the published page, and Code Injection lets you add a player across the whole site. It also has native memberships, so you can put audio behind your paywall. This guide covers per-post embeds, site-wide Auto Render, the email caveat, and members-only placement.

Two ways to do this

Per post: render in InkToAudio, then paste a player into a Ghost HTML card. Whole site: add one Auto Render snippet to Code Injection and every article gets a player on its own.

1. Get your post text into InkToAudio

  • Paste it. Open Content → Create content in InkToAudio and paste the post body.
  • Forward it by email. Copy your private forwarding address from the Forwards page and email the post to it. See the email forwarding guide.
  • Let Auto Render pull it straight off the published page (covered below).

2. Transform the text for spoken delivery

In Content → Edit, run a one-click transformation so the audio doesn’t sound like a page being read aloud:

  • Optimize for spoken content — tightens rhythm and removes written-only phrasing.
  • Podcast style — host cadence and warmth.
  • Newscast style — punchier, broadcast delivery.

Turn on Multispeaker for a two-host feel, and edit the script by hand wherever you want a specific read.

3. Pick a voice and render

Choose a voice profile (or several for multispeaker) and a delivery style — podcaster, newscaster, radio DJ, storyteller, conversational, or energetic. Click Save Changes & Render Audio.

4. Add the player to a single post (HTML card)

Click Share on the rendered post in InkToAudio and open the Script tab (website player) or Iframe tab. In the Ghost editor:

  1. Place your cursor on a new line where you want the player, click the + button, and choose HTML (or type /html).
  2. Paste the Script embed (full player, small player, or play/pause button) into the HTML card. The card runs the script on the published page.
  3. Click out of the card to see it render, then update the post.

Script vs iframe

The HTML card runs scripts, so the Script embed works directly. If a theme or proxy strips it, paste the Iframe embed into the same HTML card instead — set the height suggested in the Share dialog.

The email caveat

Ghost sends a newsletter email version of each post, and email clients can’t render HTML-card players. The inline player shows up on the web version of the post only. For the emailed version, add a plain text link or button using the Direct link from the Share dialog — for example a line near the top: “Prefer to listen? Tap here.” Web readers get the player, email readers get the link, and both count in Analytics.

Keeping audio behind your membership paywall

Ghost lets you reserve part of a post for paid members using the public preview divider. Anything below the divider is members-only.

  1. In the editor, add the Public preview divider where the free portion should end.
  2. Place your HTML card with the player below the divider. Only logged-in paid members will see and play it.

You can also set the entire post to Members only or Paid members only in the post settings — the player rides along with the gated post.

5. Add audio to every post automatically (Auto Render)

Auto Render adds a player to your current and future posts from a single snippet. Create the pipeline in InkToAudio (voice, multispeaker, transformation, allowed domains), copy the generated snippet, and add it to Ghost’s Code Injection. Full setup is in the Auto Render guide.

  1. In Ghost admin, open Settings → Code injection.
  2. Paste the Auto Render snippet into Site Footer (use the floating player mode for a footer install), then save. It loads on every page.
  3. Prefer the snippet on posts only? Use per-post Code injection in an individual post’s settings instead of the site-wide footer.

One snippet per page

Auto Render expects one snippet per article page and a single main article on the page. The post’s domain must be in your Auto Render allowed-domains list. Index and tag pages are skipped automatically.

Tip

That’s the whole loop. Render in InkToAudio, drop a player into an HTML card (gated to members if you like), or install Auto Render once for the whole site. Pair the web player with a listen link for the email version.