Remote work
Video-call data in Thailand: estimate GB for work
Two separate limits shape a mobile work call: whether the connection can carry the session at that moment, and whether the package has enough usable data for the trip. Buying more gigabytes addresses only the second. Use published meeting requirements to frame the task, then measure your own setup rather than treating a data-budget estimate as a promise of call quality.

Start with the meeting you actually attend
A one-to-one conversation, a group meeting and a presentation with screen sharing are different tasks. Choose the actual application, video setting, layout and sharing requirements before estimating the workload. Consult that application’s current documentation; do not transfer one service’s recommendations to another.
A bandwidth requirement describes connection capacity, not a fixed amount of data used every hour. Keep the capacity check separate from your observed traffic, and rehearse the real meeting on the device and connection you intend to use.
Turn a rate into an explicit planning scenario
For a decimal-GB scenario, add assumed upstream and downstream Mbps, multiply by 3,600 seconds for an hour, divide by eight to convert bits to bytes, then divide by 1,000 for GB. This assumes both rates remain constant for the whole hour. It excludes other traffic and overhead; it is neither measured usage nor an upper bound.
Illustrative assumptions only: 1 Mbps upstream plus 2 Mbps downstream sustained for one hour gives 1.35 GB. These are chosen arithmetic inputs, not requirements for Zoom, Meet or Teams. Replace them with a clearly defined scenario or use a representative allowance-counter observation for the daily budget.
| Illustrative input | Assumed value |
|---|---|
| Upstream | 1 Mbps |
| Downstream | 2 Mbps |
| Duration | 1 hour |
| Calculated decimal data | 1.35 GB |
Use editable GB assumptions for the actual call pattern and enter the product’s fast quota separately from validity. Add other scheduled traffic and a visible reserve rather than treating the call estimate as the entire day. If the reset rule or reduced speed is unknown, retain that uncertainty instead of turning the estimate into a work guarantee.
Put call assumptions inside the fast-data window →Measure a representative session, including the laptop
On a service that permits your intended use, note the provider’s remaining allowance before and after a representative call. Record the duration, application, quality setting and whether you shared a screen. Keep other traffic quiet for the test, while recognising that provider counters may not update immediately. Then compare that observation with the planning scenario.
Use the actual laptop, desk and company access tools. Watch for interrupted conversation, frozen video or failed sharing rather than accepting a download result as the whole answer. A connection can complete one task while failing another, and a measurement made on a phone outside your room is not the same acceptance check.
Record complete preflight observations only if you want a bounded comparison of the current connection to Seoul. They are not measurements of the meeting’s packet loss, jitter or quality. Use your actual application rehearsal and its own diagnostics, where available, to document the session separately.
Separate Seoul HTTP samples from the call rehearsal →Turn a short-session estimate into a day plan
Illustrative assumptions only, not a field measurement or an application requirement: suppose a settled allowance counter shows a 0.20 GB difference across a 15-minute trial with other traffic kept quiet. That is 0.8 GB per hour if the same average continues. For 3 calls of 45 minutes each, the assumed total is 2.25 hours and 1.8 GB. Add an assumed 0.6 GB for other daily activity: the subtotal is 2.4 GB. A chosen 25% reserve on that whole subtotal adds 0.6 GB, giving a 3.0 GB planning total.
This extrapolation assumes comparable traffic for every call; it is not an upper bound or a measured result from Thailand. Replace the fictional counter difference with your own observation, and do not count traffic already inside that observation again as separate call overhead. The reserve is a choice, not a guarantee. Compare the daily total with the fast-data window and expiry, then test the actual conversation and screen-sharing task separately. A GB-per-hour estimate does not establish available upload or download capacity.
Separate simultaneous calls from daily call hours
Two overlapping calls need a simultaneous-task check as well as a daily data budget. List which people, devices, calls and file transfers overlap, then rehearse that combination on a permitted connection. Adding planning rates does not measure the connection’s available capacity.
If practical, move large uploads and optional downloads outside meeting windows. On Windows, a metered setting for the hotspot Wi-Fi can reduce background data, but Microsoft notes that some updates and syncing then behave differently. It is not a guaranteed cap on every application, and necessary security updates still need an appropriate time and connection.
Put overlapping calls on a timeline
Illustrative schedule, not a capacity measurement: one person has a call from 09:00 to 09:45 and another from 09:30 to 10:15, in the same local time zone. There are 15 minutes of overlap. Moving a file upload outside that overlap changes the schedule, but the daily amount of data for the same files does not disappear. Keep the daily budget and the busiest simultaneous task list as separate notes.
Rehearse that busiest combination on the permitted setup, not just each call alone. Record whether conversation and sharing remain usable, and agree the fallback before the overlap starts. Do not infer that a package passes this check because it has enough GB, or that an HTTP sample proves the meeting will work. If the exact package does not clearly permit the intended work or sharing, keep that question unresolved regardless of the schedule.
Do not treat unlimited as permission or guaranteed performance
True and dtac’s Tourist SIM terms say maximum advertised speeds are not guaranteed, with performance depending on coverage, active users, device compatibility and environmental or technical factors. They also prohibit commercial purposes and routers or other non-handset devices. A plan label cannot certify that the intended working setup is allowed or will meet the application’s requirements.
Choose a service with appropriate terms and inspect its exact speed policy, allowance and expiry. If the provider has not clearly explained what happens after an entitlement is exhausted, leave that field unresolved. Do not infer an unlimited high-speed laptop service from an unlimited marketing headline.
Define what happens when video no longer works
Agree a fallback before an important session: a second permitted connection, a tested alternative location or an authorised switch to audio and a written follow-up. Audio is an option to rehearse, not a guarantee that a failing connection will carry the conversation.
Keep the call invitation and necessary files available offline. For the Samui–Phangan–Tao route, schedule important meetings at a tested base rather than during transfers. This guide has no ferry-route reception measurements, so a sea crossing should not be the unverified dependency behind a promised presentation.
Your next step
Make the decision concrete.
Choose the meeting profile, calculate a labelled scenario, observe a real permitted session and test the fallback before promising mobile video availability.
Practical questions
Does a one-hour video call always consume the same data?
No. The examples use explicit planning assumptions, not a fixed application consumption rate. Observe a representative session and include other daily traffic and a chosen reserve.
Can I judge call readiness by download speed alone?
No. Check upload as well, and rehearse the real call, laptop and sharing task. A transfer observation is not a meeting-quality guarantee.
Can I use one scenario for Zoom, Meet and Teams?
Not as their official requirements. Check the actual application’s documentation and measure your own representative permitted setup.
Sources & limitations
This is an independent compilation of public sources, not a first-hand network test. Terms can change; confirm the exact product before purchase. A location photograph does not establish reception.
- Metered connections in WindowsChecked 2026-10-29
- True & dtac Thailand Tourist SIM Terms and ConditionsChecked 2026-10-29