Skip to content
github-actions[bot] edited this page Nov 12, 2026 · 13 revisions

FAQ

Answers to the questions people ask most about Outpace. Each answer links to the page with the details.

What is Outpace?

Outpace is an open-source, peer-to-peer streaming engine written from scratch in Rust. It joins public, unencrypted Ace Stream (AceStream) swarms, verifies the media, and serves it over HTTP as MPEG-TS or HLS. Your player, media server or app opens a URL; Outpace handles the peer-to-peer side. It runs headless, as a server (outpace serve) or a one-shot command (outpace play). See Home.

Is Outpace an alternative to the official Ace Stream engine?

For playing public live streams, yes. It's an independent, open-source implementation that works with Ace Stream content ids and acestream:// links. It can also serve the common engine HTTP routes that existing apps call, through an opt-in compatibility mode.

It isn't a full clone. It doesn't play premium or encrypted content, and it has no accounts, web UI, search or EPG. See what's different.

Outpace isn't affiliated with or endorsed by Ace Stream. It uses Ace Stream names only to describe compatibility.

Do I need to install Ace Stream to use Outpace?

No. Outpace never downloads or runs the official Ace Stream engine or any of its libraries. You install only the outpace binary or container. If an old engine is still running on the same machine, stop it first, because both want ports 6878 and 8621.

How do I play an Ace Stream link on Linux, macOS or Windows?

  1. Download the release for your platform from Installation. There are binaries for Linux x86_64, ARM64 and ARMv7, macOS Intel and Apple silicon, and Windows x64 and ARM64.
  2. Start it: outpace serve (outpace.exe serve on Windows).
  3. Take the content id from the acestream:// link, the 40 characters after acestream://, and open http://127.0.0.1:6878/streams/ace/<content-id> in your player.

Or skip the server and play the link directly:

outpace play acestream://0123456789abcdef0123456789abcdef01234567 | vlc -

See Getting Started and Command Line.

How do I run Outpace in Docker?

docker run -d --name outpace -p 127.0.0.1:6878:6878 -p 8621:8621/tcp \
  -v outpace-data:/var/lib/outpace ghcr.io/jamezrin/outpace:0.9.0

The image is multi-arch (amd64, arm64, arm/v7). For a production setup with Docker Compose, a health check and log rotation, see Deployment.

How do I use Outpace with VLC?

Open Media → Open Network Stream and enter:

http://127.0.0.1:6878/streams/ace/0123456789abcdef0123456789abcdef01234567

Use the id of a current public stream. Add .m3u8 to the URL for HLS. From a terminal, vlc "<url>" or outpace play acestream://<content-id> | vlc - both work. See Playing Streams.

How do I use Outpace with Jellyfin, Dispatcharr or other IPTV tools?

Put the native stream URL in your M3U playlist, one entry per channel:

#EXTM3U
#EXTINF:-1,My Channel
http://outpace-host:6878/streams/ace/0123456789abcdef0123456789abcdef01234567

No handshake or compatibility mode is needed. If those tools run on another machine, make the API reachable from them, and protect it. See Playing Streams and Deployment.

My app was built for the AceStream engine. Will it work?

Probably, if it uses the common HTTP routes. Start Outpace with OUTPACE_ACE_COMPAT=1. Apps that call these then work through Outpace:

  • /ace/getstream;
  • /ace/manifest.m3u8;
  • the format=json sessions;
  • /server/api.

Apps built on the public Android SDK are among the tested clients. See Playing Streams.

Can I broadcast my own P2P live stream?

Yes. outpace broadcast my-channel creates a signed live stream that other peers can watch. Feed it MPEG-TS over HTTP, RTMP (from OBS or FFmpeg) or an HTTP pull source, or encrypted SRT in builds that include it. Peers need to reach your TCP port 8621. See Broadcasting.

Can it play premium or encrypted channels?

No. Only public, unencrypted content is supported, and that won't change.

What are the main differences and limitations compared with the official engine?

  • Content: only public, unencrypted streams.
  • No application features: no accounts, subscriptions, web UI, remote control, search, channel lists or EPG.
  • A compatibility subset: the common playback and control routes. There is no legacy seeking or file selection, and VOD isn't available through it (native VOD is).
  • Timing: Outpace buffers more by default, so streams start later but stutter less.
  • Ports: TCP 8621 for peers, with no UDP listener and no legacy port 62062.

See Migrating from AceStream Engine.

Why does a stream take a while to start?

Outpace has to find peers, then deliberately buffers before it sends the first byte, so playback rides out swarm hiccups. 20–60 seconds is normal with the defaults, and you can shorten it. See Troubleshooting.

Does it need FFmpeg?

Only for optional audio normalisation. Playback, HLS packaging and broadcasting don't use it.

Which ports do I need to open?

Only TCP 8621 inbound, if you want other peers to connect to you. Keep the HTTP API (6878) and RTMP (1935) private. No UDP port needs forwarding. See NAT and Port Mapping.

Can I rewind live TV?

For a few minutes, with Timeshift (newer than v0.9.0). It's an in-memory buffer, not a recorder, and it doesn't do EPG catch-up.

Why did my old playlist of bare infohashes stop working?

On /streams/ace/, a bare 40-character id now means a content id. Prefix infohashes with ih:, for example /streams/ace/ih:<infohash>. See Playing Streams.

Where do I report a bug?

Open an issue at https://github.com/jamezrin/outpace-stream/issues, following Troubleshooting. Please remove content ids and stream names first.

Clone this wiki locally