Wi-Fi is the first thing delegates test and the first thing they complain about. A conference can have excellent catering, a strong programme, and a comfortable room, and still be remembered as the event where nobody could get online during the keynote. Venues know this, which is why bandwidth has become one of the more contested line items in event contracts, sitting somewhere between a utility the venue should provide and a technical service the organiser should pay for.
Working out event wifi bandwidth requirements properly, before the contract is signed, is what separates an event where the network simply works from one where the organiser spends the second morning apologising.
Almost every failure traces back to the same mismatch. Venue networks are usually built for a hotel’s guest traffic, meaning a few hundred people spread across many rooms over many hours, using the connection intermittently for email and streaming. A conference inverts every one of those assumptions. Four hundred people arrive in one room, connect simultaneously, and all try to do something at the same moment the speaker says to open the app.
Density is the real problem rather than raw bandwidth, because a single wireless access point can only handle a limited number of concurrent devices well, and a ballroom designed with two access points will struggle regardless of how fast the internet connection into the building is. The second common failure is device count, since most delegates now carry a phone, a laptop, and sometimes a tablet or watch, meaning four hundred people may represent a thousand connected devices.
It is also worth remembering that not every device behaves in the same way. A phone sitting idle on the Wi-Fi is very different from a laptop downloading a large presentation or a speaker’s computer running a live cloud demonstration. The network has to cope with those different demands at the same time.
Before deciding that a venue needs an enormous internet connection, look at how the space itself is designed. The number, location, and capacity of wireless access points can matter just as much as the internet connection coming into the building.
Some useful questions include:
This is why simply asking for the venue’s “fastest Wi-Fi” does not tell an organiser very much.
Start from what people will be doing rather than from a round number. Checking email and browsing uses very little per person. Video streaming, cloud file access, and video calls use considerably more. Live streaming the event out to a remote audience is a different category again and should be treated as a dedicated requirement rather than part of the delegate allowance. The table below gives working estimates for planning purposes, though your AV provider or network supplier should confirm figures for your specific setup.
| Activity | Approximate Per Device | Notes |
| Email and light browsing | 0.5 to 1 Mbps | Baseline for most delegates |
| Social media with images | 1 to 2 Mbps | Typical conference behaviour |
| Standard video streaming | 3 to 5 Mbps | Rises sharply in HD |
| Video calls | 2 to 4 Mbps | Needs low latency, not just speed |
| Cloud file sync | 5 Mbps or more | Can saturate a link unexpectedly |
| Event app with live polling | Under 1 Mbps | Low bandwidth, high concurrency |
| Outbound live stream | 10 to 25 Mbps upload | Should be a dedicated connection |
A useful planning method is to multiply expected concurrent devices by a realistic average rather than by a peak figure, since not everyone uses the connection heavily at once, then add substantial headroom. Many experienced producers plan for somewhere between a third and two thirds of delegates being actively online at any moment, with every single one connected.
The important point is that these are planning figures, not a guarantee that a particular event will perform well at that speed. A room with poor wireless coverage can still have problems even when the available internet bandwidth looks generous on paper.
It also helps to divide users into groups when estimating demand. Delegates may mostly browse and use the event app, while speakers may need more capacity for presentations and demonstrations. Production teams, exhibitors, registration desks, payment terminals, and streaming crews can have completely different requirements.
For a larger conference, write these assumptions down before requesting a quote. It gives the venue or network provider something specific to work from instead of leaving both sides to interpret “high-speed Wi-Fi” differently.
Organisers almost always ask about download speed and almost never ask about upload, which is where events get caught out. Delegates upload constantly, posting photos and video to social media, joining video calls, and syncing files. Speakers upload presentations and demonstrate cloud products. Any live streaming, whether official or by an attendee, consumes upload capacity heavily. Many venue connections are asymmetric, offering generous download and a fraction of that upload, which is adequate for hotel guests watching films and inadequate for a room full of people broadcasting.
Ask the venue specifically for the upload figure, in writing, and ask whether that figure is dedicated or shared with the rest of the building. Latency is the third number worth asking about, because video calls and interactive applications are more sensitive to delay and packet loss than to raw throughput, and a connection that tests fast on a speed check can still make a video call unusable.
For an event with any kind of broadcast element, check:
This is particularly important when a conference is being streamed to a remote audience. A download test might look excellent while the upload side is nowhere near what the production team needs.
Treat this as a technical due diligence exercise rather than a line in the enquiry email. The questions that matter are specific, and vague answers should be treated as warnings. Ask what the total internet capacity into the building is, and how much of it will be allocated to your event. Ask whether that allocation is dedicated or shared with other events, the hotel’s guest network, and the venue’s own operations.
Ask how many wireless access points serve your specific rooms and whether they can be supplemented. Ask the maximum number of concurrent devices the network is designed to support in that space. Ask whether a hard-wired connection is available for AV, registration, and streaming. Ask who provides support during the event and how quickly they respond at nine on a Sunday morning. Ask what a network survey of your rooms would show, and whether one has been done.
It is useful to have these questions answered in writing rather than relying on a conversation with the sales team. The person arranging the booking may not be the person responsible for the venue’s network, so technical details can easily get lost between departments.
A venue that can answer these confidently usually has a network built for events, while a venue that offers only reassurance usually does not.
This is a negotiation rather than a rule, and the answer varies enormously by venue type and market. Many hotels include basic guest Wi-Fi in the room rate and charge separately for event-grade bandwidth, dedicated networks, additional access points, hard-wired drops, and technical support. Convention centres more commonly treat network services as a chargeable item with a published rate card, sometimes with exclusivity arrangements that prevent you bringing your own provider.
Charges can be structured per event, per day, per device, per access point, or per megabit of dedicated bandwidth, and the differences matter. Negotiate this at contract stage alongside room rates, because once the business is confirmed your leverage drops considerably.
When reviewing the quote, check exactly what the internet charge covers. For example:
Where the venue’s charges are high, ask what is actually included for free, whether a reduced requirement would cost less, and whether a third-party provider is permitted. Some organisers build the cost into the delegate fee rather than absorbing it, which is reasonable provided the network then genuinely works.
The key is to avoid discovering the real cost after the contract has already been signed.

Sometimes, and it is worth pricing even when you expect to use the venue. Third-party event network providers install temporary infrastructure designed for high-density use, often achieving better results than a venue’s permanent network because the design is built around your floor plan and your expected device count. The cost can be competitive with venue charges, particularly for larger events, and the service typically includes on-site engineers for the duration.
The obstacles are contractual rather than technical. Many venues restrict or prohibit third-party network installation, either through exclusivity arrangements or through rules about cabling and rigging in their building. Check this before negotiating anything, because discovering an exclusivity clause after you have quoted a third party wastes everyone’s time.
Where third parties are permitted, you will usually still need the venue’s cooperation for power, cable routes, and access during build, so the relationship matters as much as the price.
For larger conferences, bringing in a specialist can make sense when the event has several technical requirements happening simultaneously. These might include:
That does not automatically mean an external provider is necessary. It simply gives the organiser another quote against which to compare the venue’s proposal.
Technical configuration does most of the work here, and it is worth specifying rather than leaving to chance. Separate networks for different purposes prevent delegate traffic from interfering with anything critical, so AV, streaming, registration, and payment systems should sit on dedicated connections, ideally hard-wired, rather than sharing the open Wi-Fi.
Bandwidth management or quality of service rules can prioritise the traffic that matters and throttle the traffic that does not, which is how a venue prevents one person’s cloud backup from degrading the room. Per-device limits stop individual heavy users dominating. Blocking or deprioritising large downloads and peer-to-peer traffic is common practice at conferences.
On the delegate side, a simple captive portal with a clear password is better than an open network, both for security and for managing load. Ask your provider what rules will be applied, because a network with no management will perform worse than a smaller one that is properly configured.
For a busy conference, it can help to separate the network into clear categories:
This separation is not just about speed. It also reduces the risk that a problem affecting one part of the event takes down everything else.
Assume something will fail and plan the response rather than the explanation. Test the network under realistic conditions before delegates arrive, which means a load test rather than one person running a speed check in an empty ballroom. Some providers can simulate hundreds of connections, and if yours cannot, gathering your own team in the room with every device they own is a crude but useful substitute.
Identify a backup path for anything critical, which usually means a cellular connection or bonded mobile router for streaming and payments, since those are the failures that cost money rather than goodwill. Make sure a named technical contact is reachable throughout, with a phone number held by your production team rather than a general support line.
Brief front-of-house staff on the Wi-Fi name and password so delegates get a consistent answer, and put it on signage rather than relying on people remembering an announcement. Finally, have a plan for what the speaker does if the demonstration that needs internet cannot connect.
A short pre-event checklist can cover the practical details:
These steps do not make the network failure-proof, but they make a failure much easier to manage.
Honestly, the range is too wide for a useful single figure, which is why the answer has to come from quotes rather than from an article. What drives the number is the device count, the activity profile, whether dedicated bandwidth is required, how many additional access points your rooms need, whether hard-wired drops are involved, and how much on-site support you want.
A small meeting with fifty delegates checking email may need nothing beyond what the venue already provides. A thousand-delegate conference with live streaming, an event app, and a product demonstration on stage is a genuine infrastructure project with a cost to match.
The practical approach is to specify your requirement properly, using concurrent device counts and activity assumptions rather than asking for good Wi-Fi, then obtain quotes from the venue and, where permitted, a third party.
It is also useful to separate the internet cost from the wider network cost. The connection itself may only be one part of the bill. Additional access points, network configuration, cabling, dedicated connections, engineering support, testing, and backup connectivity can all contribute to the final figure.
Specifying the requirement clearly is also what protects you contractually, since a venue that agreed to deliver a stated capacity has committed to something measurable rather than to an adjective.
Good conference Wi-Fi is not simply about buying the biggest internet connection available. It comes down to understanding how many devices will connect, what delegates and production teams will actually do, how the venue’s wireless network is designed, and what happens if something fails. Work out the event wifi bandwidth requirements before signing the contract, ask exactly what the venue is charging for, and make sure critical systems have their own capacity and backup. The result is a network that quietly does its job, which is exactly what delegates expect.
Reduce Your Fees, Upgrade Your Service, Guaranteed!
Your information will not be distributed
We received your request. A payments specialist will reach out shortly.