Skip to content
Substack workflow

Turn your Substack posts into audio

Substack is built for readers. A growing slice of your audience would rather listen. Forward a post to your InkToAudio inbox, pick a voice, render — and paste the listen link back into Substack.

Read the step-by-step guide

Free trial · No Card Needed

Why Substack writers reach for InkToAudio

Substack’s editor blocks <script> tags, so most embed-based audio tools don’t work inside a post. InkToAudio is built around that constraint.

Forward, don’t re-record

Send a Substack preview email to your private InkToAudio inbox and we ingest the post — no copy, paste, or studio session needed.

Built for spoken delivery

One-click AI transformations rewrite written-only phrasing into Optimize for Spoken, Podcast, or Newscast styles before rendering.

Works around Substack’s script-tag limit

Substack blocks custom audio embeds. InkToAudio gives you a Direct Link that drops into a post or button — with full listener analytics behind it.

The full loop

From Substack draft to a listen link, in five steps

No copy-and-paste. No recording session. No re-uploads. Forward once, edit if you want to, render, and share.

01

Write and preview in Substack

Compose your post as usual, hit Preview, and share the preview email to yourself. No need to publish yet.

02

Forward it to your InkToAudio address

Open Forwards in InkToAudio, copy your private address, and forward the Substack email. The post appears in Content moments later, fully parsed.

03

Transform for the ear

Run Optimize for Spoken, Podcast, or Newscast style. Turn on Multispeaker for a two-host feel. Tweak the script directly when you want a specific line read a specific way.

04

Pick a voice and a delivery style

Choose voice profiles (one or multiple) and a delivery style — podcaster, newscaster, radio DJ, storyteller, conversational, or energetic.

05

Render and share back to Substack

Hit Save Changes & Render Audio. Once it’s done, grab the Direct Link from Share and paste it into your post — or build a custom button that links to it.

Getting the audio back into Substack

Substack won’t accept a custom player embed, but it does accept links — and that’s what InkToAudio is optimized for.

Direct Link

Recommended for Substack

A clickable listening link that works inside Substack’s content restrictions. Carries full InkToAudio analytics — plays, completion rate, drop-off points.

Embed: Link

A stylized button that links to the InkToAudio listening page. Use it as a custom button in your Substack post.

Embed: Player (script / iframe)

Full inline players. Substack blocks these inside a post, but they work great on your own website if you cross-post the same article there.

Download MP3

Grab the file and upload it to Substack’s native audio block. You lose the InkToAudio analytics, but the audio lives entirely inside Substack.

Most writers add a custom button or a one-line link near the top of the post — “Prefer to listen? Tap here.” To keep listening behind your paywall, place the link below the paywall break.

Auto Render

Publishing on a schedule? Go hands-off.

Build an Auto Render pipeline once. Every Substack post you forward to your inbox renders automatically with the voice, multispeaker setting, and transformation you chose.

  1. 1Build an Auto Render pipeline with your preferred voice, multispeaker setting, and AI transformation.
  2. 2On the Forwards page, toggle on Auto Render and pick that pipeline.
  3. 3Every post you forward to your inbox renders automatically with those settings — no manual steps.

Give your Substack a listen button

Forward one post, pick a voice, paste the link back in. Your audience picks the format that fits their day.

Forward-by-email workflow · Cancel anytime

Frequently asked questions

  • Substack blocks <script> tags and most third-party embeds inside post content. That means most embed-based audio tools won’t render. InkToAudio gives you a Direct Link that drops cleanly into a post or custom button.