VPN for remote workers and digital nomads in China

Remote work from mainland China has a specific set of problems. Zoom choppy. GitHub slow. Slack occasionally missing messages. Figma unbearable. The issue is almost always upload latency and variability — not download bandwidth. This guide is for remote workers who need those tools to work reliably.

The real constraint: upload

Chinese residential and hotel connections generally have strong download speeds (50–500 Mbps) and much weaker uploads (5–30 Mbps, frequently less at peak hours). For a remote worker this matters because:

• Zoom and Google Meet use about 1–3 Mbps up for a good video call. Upload flapping is what you hear as choppy audio
• File uploads to Google Drive, Dropbox, or your company's object storage will be slow on most Chinese connections, VPN or no VPN
• Figma, FigJam, Miro feel like they are freezing when they are actually waiting for a slow upload round-trip

A VPN cannot fix slow upload on the underlying connection. What it can do is pick a path with more stable latency, which makes video calls feel smoother even if raw bandwidth is the same.

Server selection for work

• Hong Kong for video calls — lowest latency, best choice for Zoom and Meet
• Tokyo as a backup — switch here mid-call if Hong Kong starts stuttering
• Home-country server for Git operations — GitHub and GitLab can be sluggish from East Asia, and sometimes routing through your home region is actually faster because of the return path
• Region your employer expects for any corporate SSO login that flags unusual locations

Zoom and Google Meet settings

1. In Zoom preferences, reduce video resolution to 720p. 1080p is the first thing to cut when bandwidth is variable.
2. Enable low-bandwidth mode in Meet.
3. Use a wired Ethernet connection over Wi-Fi when possible. Hotel and apartment Wi-Fi adds 20–80 ms of jitter on top of whatever the VPN adds.
4. If audio is choppy, switch to audio-only and keep video off. It helps more than you expect.

Tools that usually break and the fix

Tool	Common issue	Fix
Slack	Messages arrive slowly or out of order	Usually auto-healed by a Hong Kong or Tokyo server; try both
GitHub / GitLab	git clone hangs	Switch server, or configure a regional git proxy
Figma	Multiplayer cursor feels frozen	Hong Kong is better than Tokyo for Figma's specific backend
Notion	Pages load slowly	Notion's CDN is regional — Hong Kong is fine, Tokyo is fine
Zoom	Choppy audio	Reduce video resolution, switch to wired, try Tokyo if Hong Kong is congested
AWS console	403 errors on some regions	Use the home-country server your employer expects
Google Workspace	Works but slow	Hong Kong or Tokyo, both fine

Recommended daily setup

• Laptop always connected to Hong Kong on wired Ethernet when in the apartment
• Phone connected to Tokyo for backup use
• Router-level VPN for background devices (monitors, home automation) — router guide
• Split tunneling configured so local services (China-based APIs, local payment integration) bypass the VPN