meet.jit.si now limits meetings to 95 minutes: what to do

What changed

On October 9, 2026, the Jitsi team posted a short announcement on the official blog: “Starting today, meetings on meet.jit.si are limited to 95 minutes. More changes are coming, stay tuned!” (Jitsi blog).

Until then a meeting on meet.jit.si could run for as long as people stayed in it. The announcement gives no reason and no list of the upcoming changes.

Who it affects

Not sure which server a meeting is on? Look at the start of the meeting link. Only links on meet.jit.si are covered by this change.

What happens when time runs out

Jitsi has not published what meet.jit.si shows at the end of the 95 minutes. The open-source Jitsi Meet code has a time limit feature, added on September 1, 2026, that works like this:

• Participants see a countdown while the meeting runs.
• When it reaches zero, the meeting ends for everyone with the message “This meeting has ended because it reached its time limit. Start a new meeting to continue.”
• The same meeting name cannot be used again on that server right away, so you continue in a meeting with a new name.

Jitsi has not said that meet.jit.si uses this exact feature, so treat this as the likely behavior, not a confirmed one.

Your options for longer meetings

1. Split the meeting

For a workshop or a long class, plan a break before the 95 minutes are up and send everyone a new meeting link, for example https://meet.jit.si/TeamWorkshop-Part2. Pick a long, unusual name so strangers do not land in it. This costs nothing and needs no setup.

2. Use another Jitsi server

Many universities, companies and communities run their own Jitsi servers. If your organization has one, use it: the 95-minute limit does not apply there. Ask your IT team for the address.

3. Use 8x8 Jitsi as a Service (JaaS)

JaaS is 8x8’s paid, hosted Jitsi for embedding meetings in your own website or app, with a small free developer plan. It is the route Jitsi itself recommends for embedding, since meet.jit.si can no longer be embedded beyond a 5-minute demo (jitsi.org). Check 8x8’s current pricing before you decide. Our JaaS vs self-hosted comparison explains the trade-offs.

4. Run your own Jitsi server

Jitsi Meet is free, open-source software. On your own server there is no time limit, no sign-in requirement unless you add one, and the meetings and recordings stay with you. You pay for the server and the time to run it.

• Install Jitsi Meet with Docker or on Ubuntu with the Debian packages
• How big a server you need and what it costs per month
• Every hosting option side by side

5. Let someone run the server for you

If you want your own server without running it yourself, a managed host can do the setup and updates. One option is ours: Jitsi hosting in your own AWS account, where the server lives in your cloud account and we manage it. Jitsi Help is independent and not affiliated with 8x8 or the Jitsi project.

For server administrators: adding a time limit to your own server

Some administrators want the opposite: a limit on their own server, for example to keep a free public instance affordable. Jitsi Meet ships the Prosody module mod_time_restricted for this from release 11248 (docker-jitsi-meet stable-11248); it is not in stable-11031 and older. Enable it on the main conference (MUC) component:

On docker-jitsi-meet, in .env:

XMPP_MUC_MODULES=time_restricted
XMPP_MUC_CONFIGURATION=conference_max_minutes = 95,conference_grace_seconds = 60

Then recreate the Prosody container with docker compose up -d. On a Debian or Ubuntu package install, add "time_restricted"; to modules_enabled of the conference component in /etc/prosody/conf.avail/meet.example.com.cfg.lua, add the two options to that component, and restart Prosody with sudo systemctl restart prosody.

Leave out conference_max_minutes and every meeting ends after 5 minutes, the module’s default. A room that hit the limit cannot be recreated under the same name until Prosody restarts.

What we have not confirmed yet

• Whether meet.jit.si uses the mod_time_restricted module, and exactly what its participants see at the end. Its public config.js does not mention the countdown.
• Whether people can rejoin the same meet.jit.si meeting name after it ends.
• Whether JaaS meetings have any duration limit. The announcement does not mention JaaS.
• What the “more changes” will be.
• We have not yet enabled mod_time_restricted on one of our own servers. The settings above come from the module’s source code and the docker-jitsi-meet templates.

Sources

• Jitsi blog: Changes coming to meet.jit.si, 2026-10-09, official announcement
• jitsi.org: JaaS (embedding on meet.jit.si no longer supported), checked 2026-10-11, official page
• jitsi-meet PR #17494: time limited module and the new timer, merged 2026-09-01, source code
• mod_time_restricted.lua in jitsi-meet 11248, source code
• jitsi-meet lang/main.json (meetingTimeLimitReached message), source code
• docker-jitsi-meet Prosody template at stable-11248 (XMPP_MUC_MODULES, XMPP_MUC_CONFIGURATION), source code
• meet.jit.si config.js (disableIframeAPI: true), checked 2026-10-11, live configuration
• jitsi-meet conference constants (IFRAME_DISABLED_TIMEOUT_MINUTES = 5), source code
• jitsi-meet issue #13753, sign-in required to start meetings on meet.jit.si, 2023, community report
• 8x8 Jitsi as a Service pricing, vendor page

Need a hand?

Moving a team or a class off meet.jit.si? Talk to our engineers about a server of your own, or read about Jitsi hosting in your own AWS account.