Your sermons,
on the air, on your homepage.
Upload Sunday's recording. FaithKit finds the natural breaks, evens out the volume, and puts your preaching on a station that plays right on the front page — from your church's own server. No streaming vendor. No app to install. Nobody watching who's listening.
A little radio station that only plays your preaching.
Not a podcast feed on somebody else's platform. Not a YouTube embed with ads before the invitation. A player on your own front page, working through your own recordings, in order, all day.
Your station's clips, in the order you set, with previous / play / next on the homepage player. It just keeps going.
Upload a single clip by hand, or upload one whole service recording and let the slicer do the cutting.
In a plain folder of MP3s on your server, listed in one small file. Back it up, move it, keep it forever.
On or off from the admin. Off means the player simply isn't there — no dead widget, no "coming soon."
Upload one recording. Get a station.
The part churches dread is editing: chopping a ninety-minute service into pieces and making the volume match. FaithKit does that part for you, the moment you upload.
Listen for the pauses
The slicer scans the recording for genuine quiet — the gap after a hymn, the breath before the text is read. Silence longer than a moment (−30 dB · 0.8 s) marks a natural cut point.
Cut at the breaks
The recording is split at those pauses, never mid-sentence. Fragments shorter than three seconds are dropped; a service becomes up to twelve clean parts.
Even out the volume
Each part is normalized to broadcast loudness (−16 LUFS) with true-peak limiting, so a quiet prayer and a loud invitation sit at the same level on the listener's phone.
Put it on the air
The parts are saved as ordinary MP3s and added to your station in order. Nothing to export, nothing to paste into a feed. It's on the homepage.
One plain requirement. The slicer needs ffmpeg and Python 3 on the host. Most shared hosts don't have them — so run the slicer on a laptop (it's in the package) and upload the finished clips through the admin. The homepage player works either way. What the free install needs →
The sermon goes out. The pew comes along.
Somebody in your church listened to preaching on a radio like this one long before there was a website. The station on your homepage is the same idea, kept: your pastor’s own voice, from your own domain, for the member who couldn’t make the drive.
The ones who couldn't be in the pew.
A church website is mostly visited by people who aren't in the building. The station is for them.
The member who can't come anymore.
She has your website bookmarked. She presses play after breakfast and hears her own pastor, not a stranger on the television. No app, no login, no account.
The family deciding where to go Sunday.
Before they visit, they want to know what's preached here. Two minutes of a real message answers that better than any "About Us" page.
The dad who worked the weekend.
He didn't make it. Monday on the drive in, he opens the church site on his phone and picks up the message where the rest of the family left off.
Plain about the limits, so nobody's surprised.
We'd rather you know exactly what you're getting than find out on a Sunday.
It isn't live streaming.
The station plays services you've already recorded. If your church wants a live feed of Sunday morning, that is a separate tool with its own costs — and FaithKit will happily sit beside it.
It isn't a podcast directory.
Your clips play on your website. FaithKit doesn't push them to Apple or Spotify. Because the files are plain MP3s on your server, you can do that yourself any time — but it's your choice, not a default.
It isn't magic with a bad recording.
The slicer finds pauses and evens out loudness. It can't fix a microphone that was off or a room that echoes. A modest recorder at the pulpit makes all the difference.
Your preaching shouldn't live on somebody else's platform.
Most church audio is uploaded to a service that can change its terms, put ads in front of it, quietly count every listener — or close. FaithKit keeps the sermons where the church is.
your-church-site/
├── config/
│ └── site-config.json ← radio on/off, station name
├── data/
│ └── radio.json ← the playlist, in your order
└── media/
└── audio/
├── 2026-09-06-am-part01.mp3
├── 2026-09-06-am-part02.mp3
├── 2026-09-06-am-part03.mp3
└── … ← plain MP3s. Yours.
- Files, not accounts. A folder of MP3s and one small list. Copy it to a thumb drive and you have a backup of every message.
- Zero telemetry. The player is FaithKit's own — no third-party script, no analytics beacon, no "listening data." Who listens is between them and the Lord.
- No renewal to lose. There is no radio subscription that can lapse. Turn it on once; it works as long as the website does.
- Same on both paths. Free DIY or done-for-you managed hosting — the station is identical, and the files are still yours either way.
Press play on the sample church.
Cornerstone is a sample congregation running the real FaithKit, station included: two Scripture readings and six hymns on the air, cut by the real slicer. Listen, then join the early-access list or download it today.