ntworld.ink
AI for Research · AI in Research Practice

Using AI Remotely

What AI tools actually cost in data, and how to use them on the connections you really have in remote and regional Australia.

// take it with you Download cheat sheet (Word)
// on this page
// why this matters

Why this matters

AI tools are built and marketed by people on fast city internet. Out bush, the connection is the constraint. This page gives practical numbers for each main way of using AI (text, voice, image generation, file uploads, video), then translates them into guidance for the connections you actually meet: Telstra and Optus 4G, Starlink, venue Wi-Fi, and tethered hotspots.

// how honest these numbers are

How honest these numbers are

None of the major vendors (OpenAI, Anthropic, Microsoft, Google, Perplexity) publish official "megabytes per message" or minimum-speed figures for their chat products. The numbers below are engineering estimates, built from audio codec bitrates, typical text payloads, observed image and audio file sizes, and published Telstra and Ookla speed data. Treat them as ballparks for planning, not promises. Where a figure is a published vendor limit (such as Claude's 30 MB file cap) it is marked published; everything else is estimate.

If you plan to print a figure on a handout or quote it to a funder, check it against the vendor's current documentation first (links at the foot of the page). Bitrates and limits change as products evolve.

// data use per tool, per mode

Data use per tool, per mode

Specifics are estimates unless marked published.

Tool, modeTypical data per useMin usable bandwidth
Text chat (any tool)~2 to 80 KB per exchange~50 to 100 kbps
Voice mode (ChatGPT, Copilot, Gemini)~1 to 2 MB per minute~64 to 128 kbps sustained
Image generation~0.5 to 3 MB per imageSlow 4G works; painful on weak signal
Image upload (phone photo)~150 to 500 KB after resize; original 1 to 5 MBUpload headroom ~256 kbps+
Claude file uploadEqual to file size; 30 MB/file, 500 MB/project (published)Upload headroom matters most
Gemini Live (video plus voice)~3 to 10 MB per minute; video uplink dominates~500 kbps floor, ~1 Mbps up comfortable
NotebookLM source uploadEqual to file size; 200 MB or 500,000 words/source (published)Upload-limited
NotebookLM Audio Overview~10 to 25 MB for a 10 to 20 minute pieceDownload once, play offline
Perplexity text answer~20 to 100 KB per answer with sources~100 kbps

Four rules of thumb from this table:

// what remote connections actually deliver

What remote connections actually deliver

One signal bar is not no signal. Text tools usually work on a single stable 4G bar. What kills the experience is jitter and packet loss, not peak speed; if your bar flickers between one and zero, text chat feels frozen even if a speed test passes.

// traffic-light guide for a tethered 4g hotspot

Traffic-light guide for a tethered 4G hotspot

Green (fine on 4G): text chat on any tool; short bursts of voice; document uploads under 5 MB; reading Perplexity answers.

Amber (with care): long voice sessions (budget the data); phone-photo uploads (crop or resize first); image generation in small batches; PDFs of 5 to 20 MB; more than one person on the hotspot.

Red (prefer broadband): Gemini Live with video on; ten or more image generations; streaming NotebookLM Audio Overviews live; PDFs over 20 MB; any group activity with five or more people on the same hotspot at once.

// the voice-mode trap

The voice-mode trap

Voice feels magical and quietly eats data. One hour of voice moves roughly 60 to 120 MB each way, so 120 to 240 MB total. Nothing on home broadband, but with five people on a shared venue hotspot at once you are pushing 500 MB per hour through one phone, and it will collapse. Voice costs 10 to 20 times more than typing the same thing. If the job is to summarise a meeting or draft an email, type it; save voice for genuine hands-free moments.

// images cost far more than text

Images cost far more than text

A phone photo uploaded for the AI to look at is often 100 to 500 times the size of a text question about the same thing. On a solid connection this does not matter; on a weak bar it is the difference between a snappy chat and a hanging upload. If the AI does not need to see the exact picture, describe it. If it does, crop tight or resize first; most phones can turn a 4 MB photo into a 400 KB one without losing what matters. Do bulk image generation on broadband or Starlink.

// a month of ai use, in gb

A month of AI use, in GB

Estimated at the high end so you are not caught short.

Use profileWhat it looks likeMonthly data
LightA few text chats a day, the odd upload, no voice~0.2 to 0.5 GB
ModerateDaily text, ~30 min voice most days, occasional images, a weekly PDF~2 to 5 GB
HeavyLots of text, regular voice, Gemini Live video, bulk images, large uploads~10 to 20 GB

Even heavy individual use fits inside a normal postpaid plan (20 to 150 GB). The real gotcha is shared heavy use: one hotspot, several people, everyone on voice, nobody watching the counter, which can eat 30 to 50 GB before anyone notices.

// what works offline or cached

What works offline or cached

Honestly, nothing in the consumer tier is truly offline; ChatGPT, Claude, Copilot, Gemini, NotebookLM and Perplexity all need a live connection. "It is in Word" does not mean Copilot works without internet; every Copilot action still goes to the cloud and back.

What you can pre-cache and use without a connection: NotebookLM Audio Overviews (generate on a good connection, download the MP3, play anywhere, the single best offline-friendly feature); chat transcripts saved or exported as text or PDF; Perplexity answers exported or screenshotted; and generated images saved locally.

For genuinely offline AI, local-model tools (Ollama, LM Studio) run a small model on a laptop with no internet. Less capable than the big models and they need a reasonably modern machine, but they work on the plane, in the bush, or when the tower is down. Worth knowing about, not a first stop.

// when the connection drops mid-prompt

When the connection drops mid-prompt

On a flaky connection, type one short prompt first to anchor the chat. If you drop out, reconnect and say "continue", and the AI will usually pick up where it left off.

// a practical checklist

A practical checklist

  1. Default to text chat unless voice is genuinely needed.
  2. Crop or resize phone photos before uploading.
  3. For NotebookLM audio, generate on the best connection, download, then play offline.
  4. Do not put more than five people on one hotspot running voice or image-heavy sessions.
  5. Split big PDF uploads into smaller files on 4G.
  6. Save important conversations as text or PDF before you lose signal.
  7. Turn off video in Gemini Live on mobile data.
  8. Watch the monthly counter if you share a hotspot or prepaid SIM.
  9. On a flaky connection, anchor the chat with one short prompt first.
  10. Know the local backup with reliable Wi-Fi (library or service) for when you really need it.
// references

References

Verify any specific figure against these before printing or quoting it.

Per-tool figures are engineering estimates unless flagged as published. Re-verify against the primary sources above before printing to a participant-facing handout.

// glossary

Glossary

Bandwidth
how much data a connection can carry per second; measured in kbps or Mbps.
kbps / Mbps
kilobits and megabits per second; 1 Mbps is 1000 kbps.
Tethering
sharing one phone's mobile data with other devices.
Latency / jitter
delay and the variation in delay; high jitter makes a connection feel frozen even at decent speed.
Codec
the method used to compress audio or video; it sets how much data voice and video use.
Cached / offline
saved so it can be used without a live connection; only some AI outputs can be.
Local model
an AI model that runs on your own device with no internet, such as via Ollama or LM Studio.

Take it with you: a one-page data-cost and traffic-light cheat sheet is available to download from the button at the top of this page.