Jitsi Meet: Open-Source Video Calls Without an Account
Jitsi Meet on Android reviewed through F-Droid builds, local vs server recording, and moderator controls for password-protected, account-free rooms.
App summary
- App
- Jitsi Meet
- Developer
- Jitsi (8x8, Inc.)
- License
- Apache-2.0
- Version
- unknown
- Size
- Varies with device
- Price
- Free; no in-app purchases. Separate JaaS hosted plans are available from 8x8.
Jitsi Meet Without Google Play Services: Does the F-Droid Android Build Work?
The Android package is org.jitsi.meet, and it reaches devices through two channels: Google Play and F-Droid. That second channel is the reason this question keeps coming up. Anyone running a de-Googled phone, a hardened Android build, or a work profile with Play Services stripped out still needs a working video client, and Jitsi Meet is one of the few credible options that ships outside Google’s store. If you need a hosted meeting service with calendar integration, Google Meet is the obvious comparison, and the review explains how its call limits and battery use compare. For a mainstream meeting app with optional end-to-end encryption, Zoom is a useful comparison because the review separates its default security from the features you have to enable. If the no-account promise is what drew you to Jitsi Meet, Jami takes that idea further with peer-to-peer calling, and its review covers the tradeoffs you will notice on Android.
F-Droid compiles the app from source and signs it with its own key. Practically, that means the F-Droid build installs as a separate application from the Play version. You cannot update one over the other, and switching paths usually means uninstalling first. It also means the F-Droid build carries no Play Services dependency for the call itself, which is exactly what people without Google’s framework are looking for.
The baseline to check after installing from F-Droid is simple: open the app, create or join a room on meet.jit.si without an account, and confirm the four core functions — video conferencing, audio calls, screen sharing, and text chat. Those work without a Google login, and account-free joining on the public service is the standard the app is built around. If those four things fail, something is wrong with the install or the network, not with your lack of Play Services.
Where the two builds diverge is at the edges. F-Droid releases typically trail Play releases, so version numbers and fixes arrive later. Push notifications are the bigger practical difference: without Play Services, incoming-call and message alerts depend on the app’s own background connection, and Android’s battery management is aggressive about throttling those. Calendar integration and any hooks that lean on Google’s framework may be absent or behave differently. Check the official site and the F-Droid listing for the current build, its changelog, and any noted limitations before you commit to it as your daily client.
One more thing worth stating plainly: the Android app and the browser version are not feature-identical. If a colleague on desktop shows you a button that isn’t in your app, that’s normal, not a broken install. The stated minimum is Android 6.0 or later, though it’s worth confirming the current requirement on the official listing, since minimums move.
Recording a Jitsi Meeting on Android: Local Capture or Server-Side Feature?
Recording is the feature people most often assume exists and most often fail to find. In Jitsi’s design, recording, live streaming, and dial-in are server-configuration features, not guaranteed buttons baked into the Android client. On a stock room on the public meet.jit.si service, you may see none of them, and that is the expected behavior rather than a bug.
There’s a second constraint that catches people mid-meeting. End-to-end encryption is optional and has to be switched on deliberately, but once it is on, the server can no longer see the media stream. Server-side recording and PSTN dial-in both need that stream. So you are choosing between privacy mode and server-side capture; you cannot have both at once in the same session. Plan which one you need before the call starts, not five minutes in.
Local capture is a different route. Android’s built-in screen recorder can capture the Jitsi window and whatever audio the phone is playing or picking up through the microphone. That is a phone-level recording, not a Jitsi feature, and it shows. Quality depends on the device, the recording picks up notification sounds and echo, and the resulting file is only as good as your screen. It’s a fallback for “I need a rough copy of this,” not a substitute for a proper recording pipeline.
For dependable recording, the answer is a Jitsi host that has the recording component configured — typically a self-hosted deployment where an administrator has set up the capture service — or a paid JaaS plan from 8x8, which is built for exactly this kind of hosted capability. The free public service runs on shared infrastructure with fair-use constraints and no official 24/7 support, which is not the foundation you want under a compliance-relevant recording.
Worth clearing up a related worry: not every Jitsi call is recorded or stored somewhere in the cloud. Nothing is captured unless someone deliberately starts a recording, and on the public service there is no library of your past meetings waiting to be downloaded. The privacy risk in a Jitsi room is the same as in any meeting tool — who else is in the room — not a hidden archive.
Jitsi Meet Android Moderator Controls: Password, Lobby, and Locking Rooms Without Accounts
No account required does not mean no moderation. This is the single most common misconception about the public service, and it gets repeated by people who have never opened the in-call menu. Password-protected rooms and a lobby are both listed security features of Jitsi Meet, and both are available without anyone signing up for anything.
On the public meet.jit.si service, the person who opens the room first generally holds moderator rights for that session. From there, the Android app exposes room security through the in-call interface — a security or lock option, a lobby toggle, a password field, and participant controls for muting or removing someone. The exact placement and wording shift between versions, so the honest advice is to open the in-call overflow menu and the room information sheet and look, rather than following a screenshot from a two-year-old tutorial. The official site documents the current behavior.
The limits are structural rather than accidental. Because there are no accounts, there is no persistent identity and no account-level admin console. Moderation is per-meeting: if the moderator drops out, someone else in the room may inherit those rights, and there is no host PIN to recover. That’s fine for a team standup. It’s thin for anything where you need an audit trail of who moderated what.
Feature availability also depends on which server you’re on. A self-hosted deployment or a JaaS setup can expose considerably more administrative control — authenticated joins, moderator-only entry, recording management — because the operator controls the configuration. The public meet.jit.si service is shared infrastructure with fair-use constraints and no official 24/7 support, so treat its controls as the baseline, not the ceiling.
Jitsi Meet on Android: Battery and Mobile Data Drain During Long Calls
Every function this app performs costs power and bandwidth. Video conferencing, audio calls, screen sharing, and chat all run through the same radio and the same processor, and a long call stacks them up. Jitsi doesn’t publish per-hour consumption figures, and that’s reasonable — the number depends far more on your settings and your network than on a spec sheet.
On the public meet.jit.si service, quality and reliability depend on shared infrastructure and fair use. That has a direct effect on data consumption: a long call can see bitrate adapt up and down, reconnects after a hiccup, and stretches where the app is fighting for bandwidth. A ninety-minute call with video off on Wi-Fi and a ninety-minute screen share on mobile data are not remotely the same experience, and neither is predictable in advance.
Self-hosting changes where your media goes, not how much your phone works. Running your own server gives you control over the data path and the configuration, but the handset still encodes, decodes, and holds a radio connection for the duration. If battery life is the problem, a different server won’t fix it.
Practical measures do help. Use Wi-Fi for anything over a few minutes, turn video off when you’re not speaking, close background apps that are syncing, and keep the phone plugged in for long screen-sharing sessions. Check the in-app settings for resolution and quality options; lowering them is the most direct lever you have over both drain and data use.
A few related questions come up constantly. Screen sharing with audio depends on the Android version and how the app implements capture, so look for an audio toggle in the share dialog rather than assuming it’s there. Background blur is not a guaranteed feature on every Android device — it varies by hardware and version, and users who expect it everywhere will be disappointed. Echo and feedback are almost always acoustic: a speaker and microphone in the same room, or two devices in the same room with both unmuted. Headphones fix most of it. The stated minimum is Android 6.0 or later; confirm the current requirement on the official listing.
Pricing & Plans
The Android app is free, full stop. There are no in-app purchases, no seat count, no per-minute meter, and no account required to create or join meetings on the public meet.jit.si service. The software itself is open source under Apache-2.0, which means the code is available, auditable, and forkable.
For organizations that want someone else to run the infrastructure, 8x8 sells JaaS — Jitsi as a Service — as a separate hosted product. It includes a free developer tier capped at 25 monthly active users, with paid tiers that scale by monthly active user count. Rates change, so confirm current pricing on 8x8’s site before you budget. What you’re buying is a managed deployment with the recording, streaming, and administrative features that the public service doesn’t guarantee.
Self-hosting sits at the other end. The software costs nothing; the servers, bandwidth, TLS certificates, monitoring, and the person who maintains it all cost something. For an organization with existing infrastructure and a sysadmin, that math often works out cheaper than per-seat licensing. For a small team without technical staff, it rarely does.
Support is the honest dividing line. There is no official 24/7 support for the free public service. If a meeting breaks at 8 a.m. on a Monday, your options are the community and your own troubleshooting. Paid JaaS plans and self-hosted deployments with a support contract are where guaranteed response times live.
Who Should Use Jitsi Meet
- Teams that need to spin up a room link for an external guest without asking them to create an account first
- Schools, clinics, and public-sector groups that can self-host and want to control where meeting media is stored and routed
- Android users on de-Googled or Play-Services-free devices who need a video client available through F-Droid
- Developers building a meeting feature into a product who want an embeddable client under a permissive license
- Small groups who need a password and a lobby for a weekly call and would rather not pay per seat for it
The account-free join flow is the real differentiator. Sending someone a link and having them land in the room thirty seconds later, with no signup wall, no email verification, and no app install on desktop, removes a category of friction that commercial tools have largely accepted as normal.
The self-hosting option matters for a narrower but serious audience. Organizations that answer to data-residency rules, or that simply don’t want meeting metadata sitting on a vendor’s servers, get a path to full control. That path has a cost in maintenance, but it exists, and few competitors offer it at all.
The F-Droid distribution is a quiet advantage too. For the privacy-focused Android user who has deliberately removed Google’s framework, having a mainstream video client that installs cleanly and works without it is not a small thing.
Who Should Skip Jitsi Meet
- Users expecting WhatsApp-style persistent group chat, status updates, and a contact list that remembers everyone
- Businesses that need guaranteed cloud recording and a phone number to call when something breaks
- Marketers wanting webinar registration pages, attendee analytics, and lead capture
- Anyone who needs PSTN dial-in numbers without access to a configured Jitsi host
- Organizations that require a signed HIPAA BAA from meet.jit.si, or a fully managed service with moderation handled for them
The chat inside a Jitsi room is a meeting chat, not a messaging platform. It disappears with the room, it has no presence indicators, no read receipts, and no persistent history you can scroll back through next week. If your team’s communication lives in group chats, Jitsi is a meeting tool that sits alongside that, not a replacement for it.
Recording-heavy workflows are the other mismatch. If your organization archives every meeting by default, or runs webinars with registration and reporting, the free public service will not carry that load. You need a configured host or a JaaS plan, and at that point you’re comparing against commercial suites on their home turf.
Finally, background blur and other per-device video effects are not something to count on across the Android fleet. Users who expect every phone to blur their kitchen will be disappointed, and organizations that standardize on that expectation should test on their actual hardware first.
Comparison with Alternatives
| Feature | Jitsi Meet | Zoom | Google Meet | Element |
|---|---|---|---|---|
| Account required | No on meet.jit.si | Yes | Yes (Google account) | Yes (Matrix homeserver) |
| Free group call limit | Fair use, no fixed cap | 40 minutes | 60 minutes, 100 participants | Depends on homeserver |
| End-to-end encryption | Optional, off by default | Optional | Limited availability | On by default |
| Self-hostable | Yes (Apache-2.0) | No | No | Yes |
| Server-side recording | Requires configured host or JaaS | Local free, cloud on paid plans | Paid Workspace plans | Depends on deployment |
| Price | Free; JaaS from free tier to paid per-MAU plans | Free tier; Pro around $13.33/user/month billed annually | Free tier; Workspace Business Starter roughly $7/user/month | Free; paid hosted plans available |
Zoom is the polished option, and the gap shows in the details: cleaner admin tooling, reliable cloud recording, and a support organization behind it. The trade is the free-tier ceiling — group meetings on the free plan stop at 40 minutes — and the requirement that everyone has an account.
Google Meet wins on integration if your organization already lives in Google Workspace. Calendar links, meeting rooms, and recording all connect without extra setup, and the free tier allows 60-minute group calls with up to 100 participants. What you give up is any ability to self-host or to join without a Google identity.
Element takes the privacy argument further than Jitsi does, with encryption on by default and a decentralized Matrix backbone. The trade-off is maturity: call quality and setup complexity vary by homeserver, and the experience is less predictable than a dedicated video app. For organizations whose priority is sovereignty over the whole communication stack rather than just the call, it’s the more coherent choice.
Verdict
Jitsi Meet on Android is a credible free, account-light, self-hostable meeting client. It does the four things most meetings actually need — video, audio, screen sharing, chat — without a signup wall, and it does them on hardware that Google’s framework doesn’t touch. The optional end-to-end encryption, password-protected rooms, and lobby controls mean “no account” doesn’t translate to “no control,” even if moderation is manual and per-meeting rather than baked into an admin console.
It is not a polished Zoom replacement, and pretending otherwise does the app no favors. Recording, live streaming, and dial-in are server-side capabilities that the free public service doesn’t guarantee. Support is community-based. The interface is functional rather than refined, and the mobile app doesn’t match the browser feature for feature. If your workflow depends on archived meetings, webinar analytics, or a support line, you’ll be fighting the tool rather than using it.
Use it when the priority is getting people into a room quickly, keeping the data path under your control, or avoiding an account requirement. Skip it when the priority is a managed service with recording on by default and someone to call when it breaks. Those are different products, and Jitsi is honest about which one it is.
Pros
- Free and open source under Apache-2.0
- No account required on the public meet.jit.si service
- Can be self-hosted for full control over data and infrastructure
- Cross-platform clients for Android, iOS, web, and desktop
- Optional E2EE and room security features such as passwords and lobby
Cons
- Public meet.jit.si quality and reliability depend on shared infrastructure and fair use
- Some features such as recording, live streaming, and dial-in depend on server configuration
- UI and enterprise administration features are less polished than commercial suites
- No official 24/7 support for the free public service
- Self-hosting requires technical setup and ongoing maintenance
The link goes straight to Jitsi (8x8, Inc.). We do not host app files.
Frequently asked questions
Is Jitsi Meet free?
The recorded pricing model is Free; no in-app purchases. Separate JaaS hosted plans are available from 8x8..
What license does it use?
It is listed under Apache-2.0.
Where can I download the official version?
The official link points to https://jitsi.org/downloads/.