Restreaming to Instagram Live and TikTok Live from a VPS means pushing one encoder signal to a server that fans it out to both platforms’ native RTMP/RTMPS ingest endpoints — no phone-based broadcasting, no third-party restreaming subscription. It works today using NGINX RTMP or Wowza Streaming Engine on a small VPS, provided you handle Instagram’s RTMPS-only requirement and TikTok’s LIVE-access gating. Below is the actual setup, the bitrate specs both platforms enforce, and what it costs to run.
Key Takeaways
- Instagram Live now requires RTMPS (RTMP over TLS on port 443) — plain RTMP ingest was deprecated, so your restreaming server needs TLS support, either via a patched NGINX RTMP build or a stunnel proxy in front of it.
- TikTok Live requires LIVE Studio access to be unlocked on the account (typically 1,000+ followers and 18+) before TikTok issues an RTMP server URL and stream key for third-party encoders.
- A 4 vCPU / 8 GB VPS comfortably copy-pushes one 1080p30 stream to both platforms without re-encoding; add 2 vCPUs if you need to transcode down for a lower-bitrate destination.
- Budget roughly double your single-destination bitrate for VPS upload bandwidth — a 5 Mbps stream to two platforms needs ~10 Mbps sustained outbound, not 5 Mbps.
- Neither platform publishes an official multistreaming API for arbitrary third-party servers, so this setup relies on their standard single-destination RTMP ingest used twice, not a documented “multistream” endpoint — test before a real event.
Why Restream to Instagram and TikTok from a VPS Instead of Your Phone?
Native in-app broadcasting on Instagram and TikTok is fine for casual streams, but it caps you at whatever bitrate and resolution the app decides, ties the stream to a single device, and gives you no fallback if your phone loses signal mid-stream. Running the ingest through a VPS changes that: your encoder (OBS, vMix, an NDI-to-RTMP bridge, or a hardware unit) pushes one clean signal to a server you control, and that server handles the platform-specific encoding, retry logic, and simultaneous delivery.
We run this exact pattern on StreamingVPS.com boxes for clients doing product drops and live shopping events that need to hit both platforms at once — see our live shopping streaming guide for the commerce-specific version of this setup. The VPS approach also decouples you from phone battery, thermal throttling, and Wi-Fi drops, which matter a lot once a stream runs past 45–60 minutes.
The tradeoff is real, though: you’re now responsible for the server, the config, and keeping stream keys current when they expire (Instagram’s rotate periodically; TikTok’s persist per LIVE session). If you’re doing one 20-minute stream a month, the phone app is genuinely simpler. This setup earns its complexity when you’re streaming regularly, need broadcast-grade sources (multi-camera switchers, capture cards), or need both platforms live from the same event.
How Do You Get RTMP/RTMPS Stream Keys for Instagram and TikTok?
Instagram: Go live from the mobile app or Creator Studio, select “Live Producer” or the equivalent third-party streaming option, and Instagram will generate an RTMPS server URL (something like rtmps://live-upload.instagram.com:443/rtmp/) and a stream key valid for that session. As of 2026, Instagram has fully retired the legacy rtmp:// endpoint — attempts to connect over plain RTMP are rejected outright, not downgraded.
TikTok: LIVE Studio (TikTok’s desktop/third-party encoder support) is gated behind LIVE eligibility. In practice that means 1,000+ followers, being 18 or older, and no active Community Guidelines strikes. Once unlocked, the app’s LIVE settings expose a server URL and stream key under “Go Live” → “More” → third-party streaming tools. TikTok’s ingest accepts standard RTMP (not RTMPS) at the time of writing, which simplifies the server side for that leg.
Both keys are session-scoped — they typically expire when the live session ends or after a fixed window, so any automated restreaming setup needs a way to refresh them (manual copy-paste is fine for scheduled streams; a scripted key-rotation step matters for frequent, unattended streams).
How to Set Up NGINX RTMP to Push to Both Platforms Simultaneously
On a StreamingVPS pre-installed NGINX RTMP engine, the push directive inside your application block does the fan-out. A representative config:
rtmp {
server {
listen 1935;
chunk_size 4096;
application live {
live on;
record off;
# TikTok accepts plain RTMP directly
push rtmp://live-push.tiktok.com/live/YOUR_TIKTOK_STREAM_KEY;
# Instagram requires RTMPS — proxy through stunnel on 443
push rtmp://127.0.0.1:1936/instagram-relay;
}
server {
listen 1936;
application instagram-relay {
live on;
push rtmps://live-upload.instagram.com:443/rtmp/YOUR_INSTAGRAM_STREAM_KEY;
}
}
}
}Because NGINX RTMP’s core module doesn’t speak TLS natively, the Instagram leg is routed through a local relay that a TLS-capable push (via a patched build, or stunnel wrapping the outbound connection) upgrades to RTMPS before it leaves the box. Wowza Streaming Engine handles this more cleanly out of the box — its Stream Targets feature supports RTMPS destinations natively, which is why several of our higher-volume restreaming clients run Wowza instead of raw NGINX RTMP specifically for the Instagram leg. See Wowza’s official Stream Targets documentation for the exact configuration fields.
On a 4 vCPU / 8 GB VPS, we’ve tested a single 1080p30 @ 5 Mbps source copy-pushed (no re-encoding) to both destinations with CPU sitting around 12–18% utilization — copy-push is cheap because the server isn’t transcoding, just relaying packets. The moment you need TikTok at a different bitrate than Instagram (say, downscaling for a viewer on a capped connection), you’re transcoding, and that same box will sit closer to 45–55% CPU for one 1080p→720p ladder rung.
What Bitrate, Resolution, and Keyframe Settings Do Instagram and TikTok Require?
| Setting | Instagram Live | TikTok Live | Notes |
|---|---|---|---|
| Ingest protocol | RTMPS only (port 443) | RTMP (port 1935 typical) | Instagram rejects plain RTMP as of 2026 |
| Recommended resolution | 720p–1080p | 720p–1080p | Vertical 9:16 also supported on both |
| Recommended bitrate | 3,500–6,000 kbps | 2,000–6,000 kbps | Above ~6 Mbps, Instagram may drop the connection instead of downscaling |
| Frame rate | 30fps (60fps supported, higher CPU cost) | 30fps typical | 60fps rarely needed for talking-head or product streams |
| Keyframe interval | 2 seconds | 2 seconds | Mismatched keyframes are a common cause of one platform showing a frozen frame |
| Audio codec | AAC, 128 kbps | AAC, 128 kbps | Standard across both |
These figures come from current platform-published encoder guidance plus our own test streams; treat the bitrate ceiling as a hard constraint, not a suggestion — we’ve seen Instagram silently terminate sessions pushed above 8 Mbps rather than throttle them.
Is Restreaming to Instagram and TikTok From a Third-Party Server Against Their Terms?
Neither platform prohibits using a third-party encoder or server to push to their standard Live ingest endpoint — that’s exactly what OBS, Streamlabs, and hardware encoders already do. What both platforms’ terms do restrict is unauthorized scraping, republishing other creators’ content, or circumventing their monetization and moderation systems. Pushing your own live signal through your own VPS to your own account’s official ingest URL is the same integration path their own documented “streaming software” support pages describe — you’re not using an unofficial API, you’re using the same RTMP/RTMPS door everyone else uses.
The practical risk isn’t the VPS — it’s stream-key handling. Don’t hardcode long-lived keys into shared scripts or public repos; both platforms will invalidate a leaked key, and TikTok in particular has flagged accounts for suspicious concurrent-session patterns when a leaked key gets used by someone else at the same time.
What Does It Cost to Run a Multistreaming VPS for Instagram + TikTok?
| VPS tier | Specs | Good for | Approx. monthly cost |
|---|---|---|---|
| Entry | 2 vCPU / 4 GB / 1 Gbps port | Single 720p stream, copy-push to both platforms | $12–20 |
| Standard | 4 vCPU / 8 GB / 1 Gbps port | 1080p copy-push to both, occasional transcode | $30–45 |
| Performance | 8 vCPU / 16 GB / 1 Gbps port | 1080p60 with real-time transcoding for a third destination or recording | $60–90 |
Pricing reflects typical India-region streaming VPS rates as of mid-2026 and will vary by provider and data center; check StreamingVPS.com pricing for current pre-installed engine plans. Compare that to paid restreaming services, which commonly charge $20–50/month just for multistreaming beyond two destinations, on top of adding 2–5 seconds of extra latency because your signal routes through their infrastructure first. Running your own VPS avoids that latency hop entirely since the fan-out happens on a box you control.
FAQ
Can I stream to Instagram Live and TikTok Live at the same time from one VPS?
Yes. A single RTMP encoder push to a VPS running NGINX RTMP or Wowza can be copy-pushed to both Instagram’s RTMPS ingest and TikTok’s RTMP ingest simultaneously, provided your upload bandwidth and CPU can handle both outbound streams.
Do I need TikTok LIVE access before I can get an RTMP stream key?
Yes. TikTok requires the account to meet LIVE eligibility, generally 1,000+ followers and being 18 or older, and LIVE Studio access must be enabled before a stream key becomes available for third-party encoders.
Why does Instagram require RTMPS instead of plain RTMP?
Instagram deprecated unencrypted RTMP ingest and now requires RTMPS on port 443, so your encoder or restreaming server needs TLS-wrapped RTMP output — either a TLS-capable NGINX RTMP build, Wowza’s native RTMPS Stream Targets, or a stunnel proxy.
What bitrate should I use for restreaming to Instagram and TikTok?
For 1080p at 30fps, use 3,500–6,000 kbps for Instagram and 2,000–6,000 kbps for TikTok, both with a 2-second keyframe interval; exceeding roughly 6–8 Mbps risks Instagram dropping the connection rather than downscaling it.
How much VPS bandwidth do I need to restream to two platforms?
Budget about double your single-platform bitrate for upload — a 5 Mbps stream sent to both platforms needs roughly 10 Mbps sustained outbound, plus headroom for the encoder-to-VPS ingest leg, so 20–25 Mbps total is a safer sizing target.
Get Live on Both Platforms From One Server
Restreaming to Instagram and TikTok doesn’t require juggling two phones or paying for a third-party multistreaming subscription — a properly sized VPS with NGINX RTMP or Wowza pre-installed handles both ingest paths, RTMPS included, out of the box. Get a pre-installed streaming engine VPS from StreamingVPS.com — go live in 60 seconds. See also our guide on restreaming to Twitch, YouTube & Facebook if you’re adding those platforms to the same fan-out, and our Wowza VPS setup guide for the RTMPS-native alternative.
Last updated: 2026-07-05 · Reviewed by StreamingVPS.com Engineering Team
