# TiLive

> TiLive is a cloud TiLive live recorder. Users add a creator to the Telegram bot, TiLive checks for live sessions, records source-quality MP4, and sends the finished file plus preview media back to Telegram. Free starts at 2 watched creators with no card. Paid tiers raise watchlist and manual recording limits.

## Key facts

- Website: https://tiliverec.com
- Telegram bot: https://t.me/tiliverec_bot
- Support: 
- Public archive: 2,042 recordings, 735 creators, 906 recorded hours
- Recording format: MP4
- Recording quality: source quality, no re-encoding, no watermark
- Delivery: Telegram private chat
- Image domain: https://img.tiliverec.com
- Last updated: 2026-07-02

## What TiLive does

- Users add TiLive creator IDs, room links, profile links, or display names in Telegram.
- The watchlist checks creators about every 60 seconds.
- When a watched creator goes live, TiLive starts a cloud recording.
- The finished MP4 is delivered in Telegram after the stream ends.
- Creator pages, missed-live pages, and /live/[id] recording pages expose long-tail archive URLs for search and AI agents.

## Pricing

## Free
- Price: $0/month
- Watchlist auto-recorded creators: 2
- Manual recordings at the same time: 1
- Public archive access: included
- MP4 delivery: Telegram, source quality, no watermark
- Card required: no

## Basic
- Price: $2.99/month or $35.88/year
- Watchlist auto-recorded creators: 25
- Manual recordings at the same time: 10
- Public archive access: included
- MP4 delivery: Telegram, source quality, no watermark
- Card required: yes
- Checkout URL: https://t.me/tribute/app?startapp=sYKu

## Pro
- Price: $4.99/month or $59.88/year
- Watchlist auto-recorded creators: 50
- Manual recordings at the same time: 25
- Public archive access: included
- MP4 delivery: Telegram, source quality, no watermark
- Card required: yes
- Checkout URL: https://t.me/tribute/app?startapp=sYKy

## Recording specifications

- Format: MP4
- Video: source stream quality
- Audio: source audio
- Watermarks: none
- UI overlays: none
- Files over Telegram limits are handled as separate parts by the bot runtime.
- Storage destination: Telegram private chat.

## FAQ

### What is TiLive?
TiLive is a TiLive live recording service. It monitors creators, records live streams, and sends MP4 files to Telegram.

### How much does TiLive cost?
TiLive has a free tier for 2 watched creators. Basic costs $2.99/month for 25 creators. Pro costs $4.99/month for 50 creators.

### Does TiLive need a web account?
No. Users control recording from Telegram.

### Does TiLive record future lives automatically?
Yes. Add a creator to the watchlist once and TiLive records future live sessions when it detects them.

### Can TiLive record multiple creators at once?
Yes. Plan limits set how many creators can be watched and how many manual recordings can run at the same time.

### Where are recordings delivered?
Recordings are delivered to the user's Telegram chat as MP4 media.

### Are archived recordings free to browse?
Yes. Public creator and missed-live pages expose saved recordings, and Telegram handles delivery.

### Does TiLive record Premium lives?
Yes. TiLive detects when a room switches to Premium state during recording, keeps capturing while the source stays usable, and notifies the user when the live turns Premium and when it returns to normal.

## Top creators

- @245344416: 34 recordings, 22h 46m
- @228246471: 16 recordings, 5h 58m
- @184470667: 15 recordings, 10h 1m
- @207552302: 14 recordings, 3h 50m
- @219959674: 8 recordings, 5h 55m
- @163523863: 7 recordings, 5h 5m
- @165792853: 6 recordings, 2h 18m
- @1206994646864654338: 6 recordings, 1h 34m
- @159583966: 4 recordings, 52m 53s
- @1198367179904892928: 4 recordings, 37m 39s
- @163764864: 3 recordings, 40m 51s
- @254513628: 3 recordings, 4h 55m
- @249733628: 2 recordings, 2h 36m
- @226043810: 2 recordings, 55m 12s
- @256890783: 1 recordings, 13m 38s
- @1220924437346373632: 1 recordings, 10m 54s
- @1119887283938189313: 1 recordings, 8m 9s
- @97663107: 1 recordings, 5m 31s

## Recent recordings

- [2026-07-02 - @165792853](https://tiliverec.com/live/3724): Jishu world (9m 56s)
- [2026-07-02 - @1220924437346373632](https://tiliverec.com/live/3717): PREMİ🍭 (10m 54s)
- [2026-07-02 - @1198367179904892928](https://tiliverec.com/live/3716): hot queen 🥵 (4m 25s)
- [2026-07-02 - @1119887283938189313](https://tiliverec.com/live/3712): CrazyDoll~ Liss 🌺 (8m 9s)
- [2026-07-02 - @163764864](https://tiliverec.com/live/3723): yo*Ng$M@m$ (5m 41s)
- [2026-07-02 - @1188317867311878145](https://tiliverec.com/live/3709): vem para minha premiu 🔥🤫 (1m 55s)
- [2026-07-02 - @1245247323441147904](https://tiliverec.com/live/3708): lola (9m 27s)
- [2026-07-02 - @1207454802283573249](https://tiliverec.com/live/3692): Pasquale (26m 8s)
- [2026-07-02 - @254007828](https://tiliverec.com/live/3677): Оля🤍 (1h 21m)
- [2026-07-02 - @249733628](https://tiliverec.com/live/3670): monika (2h 9m)
- [2026-07-02 - @236008491](https://tiliverec.com/live/3550): with bakla bimbangan (9h 26m)
- [2026-07-02 - @1143076768390406145](https://tiliverec.com/live/3663): help me qu2a (2h 25m)
- [2026-07-02 - @227594394](https://tiliverec.com/live/3695): lasbo2 (57s)
- [2026-07-02 - @1136850257308602368](https://tiliverec.com/live/3684): ❣️Ayesha804✌️ (11m 42s)
- [2026-07-02 - @159583966](https://tiliverec.com/live/3688): vem pra ca😻 (23m 0s)
- [2026-07-02 - @245344416](https://tiliverec.com/live/3678): Crista (43m 28s)
- [2026-07-02 - @1279650624833699840](https://tiliverec.com/live/3685): userZZr4aHc9 (27m 45s)
- [2026-07-02 - @1275779260100866049](https://tiliverec.com/live/3672): TiLive live (1h 16m)
- [2026-07-02 - @218840200](https://tiliverec.com/live/3675): Chahat (7m 8s)
- [2026-07-02 - @1272101720164323329](https://tiliverec.com/live/3689): My brother and me 🔥hermano (16m 56s)
- [2026-07-02 - @227594394](https://tiliverec.com/live/3686): lasbo2 (10m 33s)
- [2026-07-02 - @1221360384375119872](https://tiliverec.com/live/3680): Аня (15m 12s)
- [2026-07-02 - @1238759495981891585](https://tiliverec.com/live/3673): only l3wd (10m 19s)
- [2026-07-02 - @1259329887805100033](https://tiliverec.com/live/3681): Shan (2m 17s)
- [2026-07-02 - @1206994646864654338](https://tiliverec.com/live/3679): Amelia😍 (8m 2s)
- [2026-07-02 - @254871096](https://tiliverec.com/live/3671): mina💗🤤 (58m 16s)
- [2026-07-02 - @164136921](https://tiliverec.com/live/3668): 2 in one3 (40m 55s)
- [2026-07-02 - @1272101720164323329](https://tiliverec.com/live/3674): My brother and me 🔥hermano (7m 32s)
- [2026-07-02 - @212796648](https://tiliverec.com/live/3660): 🌹🔥 (1h 20m)
- [2026-07-02 - @254513628](https://tiliverec.com/live/3662): META 4K? (1h 25m)
- [2026-07-02 - @245229264](https://tiliverec.com/live/3669): My brother and me 🔥hermano (29m 58s)
- [2026-07-02 - @219491117](https://tiliverec.com/live/3653): anjali (1h 50m)
- [2026-07-02 - @1136850257308602368](https://tiliverec.com/live/3667): ❣️Ayesha804✌️ (28m 4s)
- [2026-07-02 - @1263369417545678848](https://tiliverec.com/live/3661): CPL Chud***** (50m 25s)
- [2026-07-02 - @163864824](https://tiliverec.com/live/3665): lisa Gabriela (28m 19s)
- [2026-07-02 - @1259329887805100033](https://tiliverec.com/live/3664): Shan (25m 16s)
- [2026-07-02 - @1136850257308602368](https://tiliverec.com/live/3666): ❣️Ayesha804✌️ (20s)
- [2026-07-02 - @1245568621367738369](https://tiliverec.com/live/3659): Nina (18m 11s)
- [2026-07-02 - @1221360384375119872](https://tiliverec.com/live/3655): Аня (43m 59s)
- [2026-07-02 - @163523863](https://tiliverec.com/live/3651): ruleta🎡 x 💍 (46m 26s)
- [2026-07-02 - @254688926](https://tiliverec.com/live/3648): 🇧🇷 XMACHINE  🇺🇸 (36m 29s)
- [2026-07-02 - @159821983](https://tiliverec.com/live/3650): Rafaela (9m 30s)
- [2026-07-02 - @163864824](https://tiliverec.com/live/3658): lisa Gabriela (18m 28s)
- [2026-07-02 - @104581908](https://tiliverec.com/live/3657): hot (7m 32s)
- [2026-07-02 - @188054324](https://tiliverec.com/live/3656): Аня (22m 20s)
- [2026-07-02 - @256304261](https://tiliverec.com/live/3654): vem sentir pra*** (30m 43s)
- [2026-07-02 - @212796648](https://tiliverec.com/live/3652): 🌹🔥 (32m 10s)
- [2026-07-02 - @1163216652026204160](https://tiliverec.com/live/3639): PREM🔥 (25m 41s)
- [2026-07-02 - @1215794720942530560](https://tiliverec.com/live/3649): prem 🔥🔥🔥🔥 (12m 26s)
- [2026-07-02 - @1206994646864654338](https://tiliverec.com/live/3647): Amelia😍 (2m 46s)

## Blog corpus

## How to Record TiLive Lives to Telegram

- URL: https://tiliverec.com/blog/record-tilive-live-to-telegram
- Category: Guide
- Updated: 2026-06-16
- Summary: A practical guide to recording TiLive live streams and receiving the finished MP4 directly in Telegram.

TiLive is built for people who miss lives because of time zones, work, school, or unstable mobile notifications. Instead of screen recording manually, you add a creator and let the recorder capture the stream when it goes live.

### Use the bot as the control panel

Open the Telegram bot, send the creator ID or profile/live link, and TiLive checks whether that creator is live. If the stream is active, the bot starts a cloud recording and keeps you updated in Telegram.

When the live ends, TiLive sends the finished MP4 back to the requester. The goal is simple: no desktop app, no phone left unlocked, no manual screen recorder.

### Use IDs or links when possible

TiLive display names can include spaces, emoji, and repeated names. Numeric IDs and direct links are more stable because they point to the exact creator or room.

If a display name fails, copy the profile ID shown in the TiLive app or paste the live URL into the bot.

### Delivery happens after the stream

The recording is uploaded after the live finishes, with the video and preview carousel delivered in Telegram.

Long lives can take longer to finalize because the bot verifies duration, file size, preview frames, and Telegram upload limits before delivery.

CTA: Start with /rec for a live happening now, or /watch to save every future live from the same creator.

## TiLive Watchlist: Auto-Record Future Lives

- URL: https://tiliverec.com/blog/tilive-watchlist-auto-recording
- Category: Watchlist
- Updated: 2026-06-16
- Summary: How the TiLive watchlist works, when it checks creators, and why it is better than waiting for mobile notifications.

The watchlist is the automatic side of TiLive. Add a creator once and the recorder watches for future live sessions without you sending /rec every time.

### What the watchlist does

TiLive periodically checks watched creators. When a creator becomes live, the bot resolves the active room and starts a recording session.

This is useful for creators who go live at random times or stream while you are asleep.

### What to add to the watchlist

Use the creator ID, a profile link, or a live room link. A plain display name can work, but it is less reliable when multiple creators share the same name.

The bot stores the target and reuses the best known room information on later checks.

### How delivery works

When a watched creator finishes a live, TiLive sends the recording to your Telegram chat.

The site reads the same recorder database, so recent recordings, stats, and creator pages can update from the bot runtime.

CTA: Send /watch with a TiLive ID or link to make the next live automatic.

## TiLive ID, Link, or Username: What Should You Send?

- URL: https://tiliverec.com/blog/tilive-id-link-vs-username
- Category: Troubleshooting
- Updated: 2026-06-16
- Summary: Why TiLive IDs and live links are more reliable than display names with spaces, emoji, or duplicates.

If a recording fails before it starts, the issue is often not the recorder. It is usually target resolution: the bot must know exactly which creator or room you mean.

### Why display names are messy

TiLive names can include emoji, spaces, symbols, and non-unique text. Search results can return more than one creator for the same visible name.

A name like THEA may exist more than once. An ID such as 196725100 points to one account.

### Best input order

Use a live link first, a profile link second, a numeric creator ID third, and a display name only when you do not have anything else.

This gives the bot the cleanest path to resolve the live room and prevents recording the wrong person.

### What to do when search fails

Open the profile in TiLive, copy the visible ID, and send that number to /rec or /watch.

If the creator is live, a direct room link is even better because it includes the active context.

CTA: For the fastest start, send /rec followed by the numeric ID or live URL.

## Recording Premium-State TiLive Lives

- URL: https://tiliverec.com/blog/record-premium-tilive-live
- Category: Premium
- Updated: 2026-06-16
- Summary: What TiLive does when a live changes between normal and premium state during an active recording.

Some TiLive rooms can switch into a premium state during a session. TiLive tracks that state during recording so the bot can keep users informed while the capture continues when the stream source remains available.

### Premium state can change mid-live

A creator can begin as a normal live, switch to a premium state, and later return to normal. The recorder keeps checking the room metadata while the recording is active.

When the state changes, the bot can notify the requester without stopping the capture.

### Recording depends on the active stream source

The bot records from the stream source it can resolve. If the source remains usable, the recording can continue across premium-state transitions.

If TiLive changes the media session or blocks the source, the recorder handles the failure path and marks the recording accordingly.

### Why status messages matter

Premium-state alerts are useful operational signals. They explain why a live looks different in the app while the bot is still working in the background.

They also make future plan gating possible without changing the recording engine.

CTA: Keep the bot running and let the recorder report state changes instead of restarting manually.

## TRTC vs Agora in TiLive Recording

- URL: https://tiliverec.com/blog/trtc-vs-agora-tilive-recording
- Category: Tech
- Updated: 2026-06-16
- Summary: A plain-English explanation of the two live transport paths TiLive may use and why the recorder supports both.

Live apps can use different real-time media providers. TiLive rooms may expose TRTC-style metadata or Agora-style metadata, and a serious recorder must handle both paths.

### Why HTTP links are not always enough

Some lives expose HLS, FLV, or other HTTP-playable URLs. Those are straightforward for FFmpeg.

Other lives expose real-time RTC metadata. In that case the recorder must join the media session with the right parameters instead of guessing a fake CDN URL.

### TRTC and Agora need different runtime handling

TRTC and Agora sessions do not look identical. They can have different app IDs, channels, users, signatures, tokens, and stream identities.

TiLive keeps those paths separated so one provider fix does not break the other.

### What users should notice

Ideally, nothing. The bot should say that recording started, then deliver the final MP4 after the live ends.

The transport details are operational details for reliability, not steps the Telegram user should have to manage.

CTA: Use the same /rec and /watch commands; TiLive chooses the recorder path behind the scenes.

## Telegram Delivery: Video Plus Preview Carousel

- URL: https://tiliverec.com/blog/telegram-video-delivery-preview-carousel
- Category: Telegram
- Updated: 2026-06-16
- Summary: How TiLive packages a finished recording with the MP4, timestamped preview frames, duration, size, and watchlist hint.

Delivery is part of the product experience. A good recorder does not just dump a random file into chat; it sends context, duration, size, and a preview that helps the user identify the live.

### The MP4 stays first

TiLive sends the video as the primary media item so Telegram treats it as a playable video, not a document attachment.

The preview carousel is generated separately from timestamped frames, giving a quick visual summary of the live.

### Why the archive comes first

The service can upload to a private archive group before delivering a clean copy to users.

That archive-first flow keeps an internal copy while avoiding the suspicious forwarded-message header in user chats.

### Clean local storage

After successful delivery, local recording files and generated preview frames should be deleted.

This keeps VPS disk usage predictable and prevents old recordings from filling the server.

CTA: Check /status during a live, then wait for the final playable video after the stream ends.

## TiLive Recorder vs Manual Screen Recording

- URL: https://tiliverec.com/blog/tilive-recorder-vs-screen-recording
- Category: Comparison
- Updated: 2026-06-16
- Summary: Why a cloud recorder is better than leaving your phone or browser open to capture a TiLive session.

Manual screen recording works until it does not. Battery, notifications, network drops, accidental locks, and time zones all make it unreliable.

### Cloud recording is unattended

With TiLive, the bot and recorder run on a server. Your phone does not need to stay unlocked and your browser does not need to stay open.

That matters most for long lives and creators who stream late at night.

### The output is easier to keep

A manual recording often ends up as a local file that needs trimming, moving, and backing up.

TiLive sends the finished MP4 directly to Telegram, where it is easy to replay and search later.

### Automation catches more lives

A watchlist can start when a creator goes live. Manual recording only starts if you notice the live in time.

That gap is the main reason people use a bot instead of a phone recorder.

CTA: Use /watch for creators you care about and stop relying on push notifications.

## Rate Limits for TiLive Recording Bots

- URL: https://tiliverec.com/blog/tilive-live-recorder-rate-limits
- Category: Ops
- Updated: 2026-06-16
- Summary: How a recorder should avoid hammering TiLive and Telegram while still catching lives quickly.

Live recording automation needs discipline. Poll too slowly and you miss streams; poll too aggressively and APIs start pushing back.

### Separate TiLive checks from Telegram sends

TiLive lookups and Telegram uploads have different limits. A clean architecture keeps separate gates for source checks, bot commands, and outbound messages.

This prevents one busy workflow from starving the rest of the bot.

### Deduplicate active recordings

If five users request the same live, the service should run one recording and attach all requesters to it.

That saves CPU, bandwidth, storage, and upload time while keeping the user experience identical.

### Use clear failure states

Offline, user-not-found, auth-required, rate-limited, and stream-resolve errors should produce different user messages.

Those distinctions make support much easier and reduce repeated commands from confused users.

CTA: Keep watchlist polling steady and let command cooldowns absorb impatient retries.

## SEO for a TiLive Public Recording Archive

- URL: https://tiliverec.com/blog/tilive-recorder-seo-public-archive
- Category: SEO
- Updated: 2026-06-16
- Summary: How TiLive can expose useful public pages for creators, latest recordings, stats, guides, and glossary terms.

A recorder SaaS should not rely on a single landing page. Search traffic comes from many specific intents: recorder, pricing, creator archive, troubleshooting, and comparisons.

### Use one URL per intent

The homepage explains the product. Pricing answers plan questions. Latest recordings and creators show live product activity.

Blog posts answer how-to, troubleshooting, and comparison searches without cluttering the main app surface.

### Keep metadata specific

Each post should have a focused title, description, canonical URL, Open Graph data, and structured Article metadata.

A sitemap helps crawlers discover the blog and product pages without guessing.

### Connect content to the bot

Every guide should give a practical next step, usually opening the Telegram bot or explaining which command to use.

That turns SEO pages into onboarding, not just text.

CTA: Publish focused guides and keep internal links between blog, pricing, latest, creators, and Telegram.

## Troubleshooting TiLive Recording Audio Delay

- URL: https://tiliverec.com/blog/fix-tilive-recording-audio-delay
- Category: Troubleshooting
- Updated: 2026-06-16
- Summary: What can cause delayed or crackling audio in a live recording and how a recorder runtime should isolate the source.

Audio drift is one of the most annoying live recording bugs because the video can look fine while the voice slowly falls behind or starts crackling.

### Common causes

RTC capture can drift when the runtime mixes local and remote audio incorrectly, captures the wrong source, or records at unstable frame timing.

CPU pressure can also cause audio gaps if the recorder process cannot keep up with the incoming stream.

### Prefer remote stream audio

For server-side recording, remote media audio is usually the safest default. It avoids capturing local system sound or double-mixing audio.

The recorder should keep this configurable, but the default should match the real production path.

### Verify with ffprobe and preview

After recording, verify the output duration, dimensions, and file size before delivery.

Short smoke recordings are useful because they expose drift and crackling before users wait through a long live.

CTA: If audio sounds slow or crackly, test the same creator with the remote audio path before changing video settings.

## Deploying a TiLive Recorder on a VPS

- URL: https://tiliverec.com/blog/deploy-tilive-recorder-on-vps
- Category: Deploy
- Updated: 2026-06-16
- Summary: A production checklist for running the TiLive bot, admin panel, and public site on a VPS.

Before pointing a domain at the service, the VPS needs a clean runtime: recorder process, database path, web build, admin secret, FFmpeg, Node runtime, and persistent logs.

### Install the media dependencies

FFmpeg and ffprobe must be available in PATH. Node is also required for the native RTC recorder scripts.

The Agora and TRTC recorder scripts should be installed with their own package dependencies before the bot starts.

### Keep one database path

The bot writes to SQLite and the web/admin apps read the same database. Configure RECORDER_DB_PATH or DATABASE_PATH consistently.

If the site points at a different database, the public pages will look stale even while the bot records correctly.

### Run processes separately

Use a process manager for the bot and the two Next apps. Restarting the web app should not kill an active recording.

Keep recordings on a disk with enough temporary space because uploads happen after the live finishes.

CTA: Before DNS, run bot, web, and admin locally against the same SQLite file and verify a recording appears on the site.

## What a TiLive Recorder Admin Panel Should Control

- URL: https://tiliverec.com/blog/tilive-recorder-admin-panel
- Category: Admin
- Updated: 2026-06-16
- Summary: The operational controls a TiLive admin panel needs: active recordings, users, plans, tickets, logs, watchlist, and system health.

A recorder backoffice is not a dashboard decoration. It has to let the operator act: change plans, ban users, open tickets, inspect recordings, and see whether the recorder is healthy.

### User controls must write to the database

Plan changes and ban states should not be mock buttons. They need server-side routes and persistent database fields.

That way the admin panel reflects the same state the bot and public site can use.

### Tickets need status and notes

Support tickets should be creatable from the admin, tied to a Telegram user, and moved between open, waiting, and closed.

Internal notes help track what happened without scattering support context across chats.

### Recorder views should stay operational

Active recordings, logs, watchlist cycles, CDN health, and system metrics are for daily operations.

They should be dense, predictable, and tied to real data as the backend matures.

CTA: Use the admin panel to change user state and support tickets from one place before scaling traffic.

## Glossary

- Watchlist: Creators TiLive monitors automatically.
- On-demand recording: A one-shot /rec command for a creator outside the watchlist.
- Source quality: The original stream quality captured without re-encoding.
- Telegram delivery: The MP4 is sent directly to the user's Telegram chat.

## Machine-readable facts

- Pricing markdown: https://tiliverec.com/pricing.md
- Facts JSON: https://tiliverec.com/api/facts.json
- Short LLM directory: https://tiliverec.com/llms.txt
- Sitemap: https://tiliverec.com/sitemap.xml