Question 1

Why can't I share my camera?

Accepted Answer

We made a deliberate decision not to support camera sharing right now. As a small team, video introduces a significant compliance and moderation burden - content policies, detection requirements, storage implications - that we're not in a position to handle responsibly at this stage. We'd rather get it right than get it fast.

Question 2

Why can't I share images or GIFs?

Accepted Answer

Direct image uploads are on the roadmap. We plan to support GIFs via a plugin model so the content comes from established providers rather than being user-uploaded. The reasoning is the same as camera sharing - managing arbitrary user-uploaded media responsibly is a compliance burden a small team can't take on lightly.

Question 3

Do you track anything?

Accepted Answer

We collect the minimum needed to run the service - account data, server membership, and infrastructure-level usage metrics. We do not track, read, or log message content or voice activity. No third-party analytics, no ad attribution, no profiling.

Question 4

Why do messages disappear after 24 hours?

Accepted Answer

Messages are automatically deleted 24 hours after being sent. This is currently driven by cost and scale - as of March 2026 we have over 1,500 servers with an average of 4 users each, and storing full message history indefinitely adds up quickly for a small operation. This may change as our infrastructure scales, but 24 hours is the rule for now.

Question 5

What is Lag?

Accepted Answer

Lag is an ultra-low-latency voice communication platform built for competitive gaming. It delivers sub-50ms voice latency with a lightweight native desktop client built in Rust - no Electron, no bloat.

Question 6

How do I create a server?

Accepted Answer

After signing in, click the "+" button on the server rail to create a new server. Give it a name, and you're ready to go. Invite your squad by sharing the server invite code or link.

Question 7

What platforms does Lag support?

Accepted Answer

Lag has a native desktop client for Windows and Linux, plus a full-featured web client that works in any modern browser. A mobile app is in development.

Question 8

How do I invite friends?

Accepted Answer

Open your server settings and create an invite link. Share it with your friends - they can join directly from the link. You can also add friends by username and send direct messages.

Question 9

What latency can I expect?

Accepted Answer

Lag targets sub-50ms median voice latency through region-routed SFU infrastructure. Voice packets take the shortest path between you and your squad, with 99.2% packet recovery through redundant encoding.

Question 10

What audio codec does Lag use?

Accepted Answer

Lag uses Opus at 48kHz, the same codec used by professional streaming and gaming platforms. The audio pipeline is tuned specifically for gaming callouts rather than conference-room speech.

Question 11

How much CPU does Lag use?

Accepted Answer

Under 1% CPU while idle in voice. The desktop client is built in Rust with Tauri - not Electron - so your game keeps resource priority. Lag is designed to be invisible to your system.

Question 12

What is adaptive streaming?

Accepted Answer

Lag uses 3-layer simulcast that automatically adjusts audio quality to each listener's connection. If someone has a weaker connection, they get a lower bitrate stream without affecting anyone else.

Question 13

Can I self-host Lag?

Accepted Answer

Yes. Lag is fully self-hostable. Deploy your own voice infrastructure using our Docker images and Terraform configurations. You get complete control over your voice servers and data.

Question 14

What do I need to self-host?

Accepted Answer

You need a Linux server (or cloud VM), Docker, and a PostgreSQL database. Our infrastructure-as-code configs handle the rest. Check the self-host page for detailed deployment guides.

Question 15

Is the self-hosted version feature-complete?

Accepted Answer

Yes. The self-hosted version has full feature parity with the hosted service. Voice rooms, servers, direct messages, friend lists - everything works the same.

Question 16

Does Lag record or store voice data?

Accepted Answer

Never. Voice packets are relayed in real-time through our SFU infrastructure and are never recorded, stored, or processed. Once a voice packet is delivered, it's gone.

Question 17

Does Lag sell user data?

Accepted Answer

No. Lag does not sell, share, or monetise user data in any way. There are no tracking pixels, no ad profiles, and no data brokers. Your data stays yours.

Question 18

How does authentication work?

Accepted Answer

Lag uses OAuth sign-in through Discord or Google. We never store passwords. All API requests are authenticated with JWTs, and every database table has row-level security enabled.

Question 19

Is Lag open source?

Accepted Answer

Lag's deployment infrastructure and voice server components are open for self-hosting. We're committed to transparency about how your data is handled and how the platform operates.

Question 20

Is Lag free?

Accepted Answer

Yes. Lag is completely free to use with no feature gates, no per-seat pricing, and no premium tiers. Create servers, join voice rooms, send messages - all free.

Question 21

Are there user limits?

Accepted Answer

No artificial user limits. Your server can have as many members as you need. Voice room capacity is determined by infrastructure, not licensing.

Question 22

Will Lag always be free?

Accepted Answer

Core voice and messaging features will always be free. If we introduce premium features in the future, they will be optional extras - the core experience will remain free and fully functional.

Quick answers to common questions.

Common Questions

Getting Started

Voice & Performance

Self-Hosting

Privacy & Security

Pricing

We'd love to hear from you.