How Tuneline Works: You Bring the Source, We Just Play It

"Zero content" is easy to say and vague if you don't explain the mechanism. Here's what actually happens, step by step, when you add a source to Tuneline.

Step 1: You provide a URL

Every source in Tuneline starts the same way — you paste in an address. That might be a direct M3U playlist link, or Xtream Codes credentials that resolve to one. Either way, the input is a URL (or the pieces needed to build one) that you already had before you opened the app.

Tuneline ships with this field empty. There's no default, no suggestion, no pre-filled example that points anywhere real.

Step 2: The device talks directly to that URL

This is the part that matters most. When you add a source, your device — not a Tuneline server — makes the connection to it. The playlist is fetched client-side, parsed on-device, and rendered in the app's UI. When you press play on a stream, your device opens a connection to that stream's own server and decodes what comes back, in real time.

Tuneline's own infrastructure is not in that path. There is no step where a stream is pulled onto a Tuneline server, cached, transcoded, or relayed back out to you or to anyone else. The data path is device → your source's server, directly, the same way a browser's video tag talks directly to whatever URL is in its src attribute.

Step 3: What Tuneline's servers actually do

Tuneline does run servers — for account sync, so your list of sources and favorites shows up on your other devices; for licensing, to check whether an account has purchased Pro features; and for the usual application housekeeping (crash reports, update checks). None of that involves the content itself. The sync service stores the address of a source you added (so your other device can fetch it the same way yours does), not a copy of what's playing at that address.

If every server Tuneline operates went offline at once, playback would keep working — because playback was never routed through them in the first place.

Step 4: Nothing persists beyond what you ask for

By default, Tuneline plays a stream and moves on — no copy of it is kept anywhere. What is stored, locally on your device and account-synced if you're signed in, is metadata you control: your list of sources, which channels you favorited, what you last watched (so you can resume), and an electronic program guide if your source provides one. That's configuration and history about your usage, not a copy of the content itself.

The comparison that makes this concrete

This is the same architecture as a web browser. A browser doesn't host the pages it renders — it fetches whatever URL you navigate to, directly, and shows you what's there. Nobody expects the browser vendor to have reviewed or to be responsible for every page ever opened in it, because the browser's job is rendering, not publishing.

Tuneline's job is the same, scoped to audio/video streams instead of web pages: fetch what you point it at, render it well, remember your preferences. The source is always yours to choose.

Related reading

• What Tuneline Actually Is (And Isn't) — the plain-language version of this same architecture
• Tuneline's Content Policy — the policy implications of this design
• What the source formats actually are

---

— Shamir