QuickQ documentation and help centre

From a first install to protocol selection, split tunnelling and router-wide deployment. This documentation is maintained by the QuickQ engineering team and kept in sync with client v6.4.2.

Applies to v6.4.2 Last updated 13 October 2026 About 12 minutes to read

1. Quick start

Using QuickQ takes three steps: download the client, sign in, click connect. On launch the client benchmarks available nodes and recommends the lowest-latency route for your current network.

Before you begin

An email address you can access, used for registration and password recovery;
Any working internet connection — home broadband, mobile data or corporate network;
For the router build, a router model and firmware version that meets the requirements below.

Tip: for your first session, connect once with the default settings before tuning protocols and routing rules. It makes any later problem much easier to isolate.

2. Windows setup

The Windows client supports Windows 10 1809 or later and Windows 11, with a graphical interface, tray control and launch-on-startup.

Installation

Download QuickQ-Setup-x64-6.4.2.exe from the download page;
Verify it with certutil -hashfile QuickQ-Setup-x64-6.4.2.exe SHA256;
Run the installer and follow the wizard. Windows will ask to install a virtual network adapter driver — allow it;
Launch the client and sign in with your email. The first sign-in authorises the device.

Recommended settings

Protocol: QuickQ Turbo by default; switch to IKEv2 if your network restricts UDP traffic.
Kill Switch: leave it on so traffic never leaks when the tunnel drops.
Launch on startup: enable it in Settings → General so protection is up from boot.

3. macOS setup

The macOS build is a universal binary that runs natively on both Apple Silicon and Intel, with a menu bar panel for day-to-day control.

Installation

Download QuickQ-6.4.2.dmg and verify its SHA-256;
Open the disk image and drag QuickQ into Applications;
On first launch, allow QuickQ to load its system extension in System Settings → Privacy & Security → Network;
Sign in, then connect from the menu bar icon.

Note: if the authorisation prompt does not appear in Privacy & Security, run sudo killall -HUP mDNSResponder in Terminal to refresh network services, then reopen the client.

4. iOS and Android setup

Mobile clients build the tunnel through a system network extension on iOS or VPNService on Android, and stay alive in the background with a low-power keep-alive.

iOS / iPadOS

Search for QuickQ on the App Store, or use the link on the download page;
On first connect, allow the app to add a VPN configuration;
Enable Background App Refresh for QuickQ in Settings → General so it reconnects after a network change.

Android

Install from Google Play, or download the APK from this site;
Allow installation from unknown sources if you are using the direct APK;
Authorise the VPN service on first connect;
To avoid battery optimisation killing the tunnel, set QuickQ to Unrestricted in Settings → Battery.

5. Linux command line and router deployment

Whole-network acceleration at the router suits homes and small offices with smart TVs, consoles and IoT devices — configure once and every client is covered.

Linux command line

# Install the client
curl -fsSL https://dl.quickqapi.com/install.sh | sh

# Sign in and list available nodes
quickq-cli login
quickq-cli nodes --region hk

# Bring up the tunnel as a background daemon
quickq-cli connect --node hk-01 --daemon

OpenWrt router

Confirm the firmware is OpenWrt 21.02 or later;
Install quickq-core and luci-app-quickq from System → Software;
Open the QuickQ menu in LuCI and enter the device key issued to your account;
Select the clients or subnets that should use the accelerated path under Policy Routing.

6. Advanced settings

Choosing a protocol

Protocol characteristics and recommended use
Protocol	Transport	Latency	Best for
QuickQ Turbo	QUIC / UDP	Best	Gaming, streaming, everyday use
WireGuard	UDP	Excellent	Mobile, frequent network changes
IKEv2	UDP 500/4500	Good	Restricted networks, corporate firewalls
OpenVPN	TCP 443	Fair	Networks that block UDP entirely

Per-app split tunnelling

With split tunnelling on, each application can be set to use the accelerated path, go direct, or follow the global setting. The usual pattern is to accelerate games and streaming while letting banking apps and local NAS traffic go direct, avoiding unnecessary detours.

Windows / macOS: Settings → Split tunnelling → add app rules;
Android: Settings → Per-app proxy, tick the apps to accelerate;
iOS: system limits mean only global and per-domain routing are available.

Custom DNS

QuickQ uses encrypted DNS by default, which protects against DNS hijacking. If you run your own resolver, enter it under Settings → Advanced → DNS and the client will validate responses to prevent leaks.

7. Security and compliance

Encryption and key management

Every tunnel uses AES-256-GCM with X25519 elliptic-curve key exchange for forward secrecy. Session keys rotate every 45 minutes by default, so a single compromised session key cannot decrypt historical traffic.

Leak protection

DNS leak protection: all lookups are forced through the encrypted resolver inside the tunnel;
IPv6 leak protection: prevents traffic bypassing the tunnel on IPv6 networks;
Kill Switch: freezes network access if the tunnel drops, keeping your real IP hidden.

No logs and audits

QuickQ does not record browsing history, connection destinations or DNS query contents. We commission an independent security firm to run penetration tests and code reviews every year; the most recent audit (September 2026) found no high-risk issues. See the summary on the product updates page.

8. Troubleshooting

Connection failures

Confirm the local network works: load any ordinary website on the same device;
Switch protocol: QuickQ Turbo → WireGuard → IKEv2;
Change node: prefer lines below 60% load;
Change port: on restricted networks set the port to 443;
Close conflicting software: other VPNs, proxy extensions and deep packet inspection suites.

Speeds below expectations

Measure your raw local bandwidth first to rule out a broadband bottleneck;
Pick a node in the same or a neighbouring region as the target service;
Enable split tunnelling so local traffic does not consume tunnel bandwidth;
On routers, check the CPU is not the limit — a model with hardware acceleration is recommended.

Submitting a diagnostic log

If none of the above helps, generate a log from Settings → Export diagnostic log and send it to the support page together with your OS version, client version, selected node and the time the problem occurred. The log contains no browsing history and is used only to diagnose network issues.

9. Glossary

Accelerator: A network tool that builds an optimised route between the client and the target service to reduce latency and jitter and improve stability.
Encrypted tunnel: An encrypted channel across a public network whose contents cannot be read by a third party.
No-logs policy: A provider commitment not to record browsing history, connection destinations or traffic contents, keeping only the minimum data required for accounts and billing.
Kill Switch: A safety mechanism that cuts network access when the accelerated connection drops, preventing real IP exposure.
Jitter: How much latency varies over time. Lower jitter means more consistent gaming and real-time voice quality.
Split tunnelling: A policy that decides per app or domain which traffic uses the accelerated path and which goes direct.

Not covered here? Contact 24/7 live support or browse more answers on the FAQ page.