Skip to content
Migration guide

Switching from Trinity Audio to InkToAudio

If you use Trinity Audio to add a listen player to your articles, InkToAudio will feel familiar. You get the same auto-embed approach plus a second workflow for newsletters and one-off issues — and a clear path to move both across.

For publishers

Free trial · No credit card needed

What carries over

Trinity Audio turns written content into audio for publishers. InkToAudio does the same — and the two workflows below cover every page on your site.

The auto-embed you already use

One snippet on your article template gives every story — current and future — an audio player. Same idea as the Trinity Audio code, no per-article work.

A second way in for one-offs

Email or paste an article or newsletter issue and get a hosted, embeddable player back. Useful for content that does not live on an auto-embed template.

Voices, feeds, and analytics

180+ studio voices, voice cloning, multi-speaker audio, hosted podcast RSS, translation, and listener analytics — all under one account.

Workflow 1

Auto embedding for every article

This is the direct replacement for the Trinity Audio embed code. In InkToAudio it is called Auto Render: install once, and every article page gets a player on its own.

01

Create an Auto Render setup

In the InkToAudio dashboard, open Auto Render and create a setup. Pick the voice, player style, colors, languages available (with auto translation), and inline or floating placement, then list the domains allowed to use it.

02

Copy the one-line snippet

Auto Render generates an embed snippet tied to that setup. It carries a script ID and a private token — the same install pattern you know from Trinity Audio.

03

Paste it into your article template

Drop the snippet into your CMS article template or theme — exactly where the old auto-embed code lived. WordPress, Ghost, Webflow, and custom templates all work.

04

Every article gets a player

When a reader opens an article, InkToAudio reads the page, generates the episode, and shows the player. New articles are covered automatically — no extra steps.

The Auto Render snippet

<script
  id="tts-reader-script"
  src="https://inktoaudio.com/api/auto-render/YOUR_SCRIPT_ID/script.js"
  data-script-id="YOUR_SCRIPT_ID:YOUR_TOKEN"
  data-publish-date=""
></script>

Prefer a fixed player? Auto Render also supports a floating mode and a custom mount point.

Workflow 2

Create content, then embed the player

Not every issue lives on an auto-embed template. For newsletters, standalone pages, and one-offs, create the episode directly — two ways in, one embeddable player out.

Email it in

Forward a newsletter issue from Substack, Beehiiv, Mailchimp, or ConvertKit to your private InkToAudio inbox address. InkToAudio parses the email and creates a ready-to-render draft.

Paste it in

Open Create Content, paste your article text or HTML, choose a voice profile and delivery style, and click Create audio. AI helpers can smooth the script for listening first.

Then drop the player anywhere

Once the episode renders, the Share dialog gives you a script embed, an iframe, a direct listen link, an email-safe button, and an MP3 download. The same episode also flows into your podcast RSS feed and the self-updating Latest Content Widget.

Iframe embed

<iframe src="https://inktoaudio.com/embed/YOUR_EPISODE_ID" width="100%" height="180" frameborder="0" allow="autoplay"></iframe>

Trinity Audio, translated

Every concept you rely on has an equivalent in InkToAudio.

In Trinity Audio
In InkToAudio
Auto-embed code / WordPress plugin
Auto Render snippet — one script tag for your article template
Player theme, position, and floating button
Auto Render player style: colors, inline placement, or a floating player
Per-post voice and source language
Per-post voice profile plus translation languages
Trinity CMS channels, playlists, and RSS export
Hosted podcast RSS feeds plus the self-updating Latest Content Widget
Real-time translation
Translation languages applied across both publishing workflows
Audio advertising
Sponsor intro and outro clips, premium feeds, and listener analytics

Your move, in four steps

You can keep Trinity Audio live while you set InkToAudio up — there is no hard cutover.

Step 01

Create your account and a voice

Start a free trial, then create a voice profile from the studio library or clone your own voice. This becomes the default narrator for both workflows.

Step 02

Rebuild your auto-embed as Auto Render

Create an Auto Render setup that mirrors your Trinity Audio install: same allowed domains, a matching player style, and your chosen voice.

Step 03

Swap the snippet — side by side if you like

Replace the Trinity Audio code in your template with the InkToAudio snippet. You can install it on one section first, confirm it, then roll it out everywhere.

Step 04

Route issues and one-offs through Create Content

For newsletters and pages outside your article template, forward them to your inbox address or paste them into Create Content, then embed the player.

Bring your audio to InkToAudio

Set up Auto Render for your site and create your first episode in the same afternoon. No credit card, no commitment.

Hosted podcast RSS · 180+ voices · Cancel anytime

Frequently asked questions

  • Yes. The Auto Render workflow adds an audio player to your current and future articles from a single snippet on your article template — the same auto-embed approach you use in Trinity Audio.