QuickRemote connects directly to VNC and supported RDP endpoints that you control. Protocol availability differs by the device running QuickRemote, so check the platform table before creating a profile.
Platform Availability
| QuickRemote device | VNC | RDP |
|---|---|---|
| Mac | Built into QuickRemote | Built into QuickRemote. You can instead choose another installed RDP app. |
| iPad | Built into QuickRemote | Built into QuickRemote. |
| iPhone | Built into QuickRemote | Not listed for this release. |
| Android | Built into QuickRemote | Not listed until physical-device release verification is complete. |
| Windows | Built into QuickRemote | QuickRemote creates a profile and opens Windows Remote Desktop (mstsc). |
System requirements: iOS/iPadOS 15 or later, macOS 13 or later, and Android 7.0 (API 24) or later. Macs that cannot update to macOS 13 remain on the last compatible store version. The Windows requirement is unchanged because Windows RDP continues to open in
mstsc.“Built into QuickRemote” and “open another app” are different features. On Windows, the RDP window belongs to Windows Remote Desktop. On Mac, QuickRemote asks whether to use its built-in RDP view or another installed RDP application.
Prepare the Remote Computer
QuickRemote is the viewing and control client. The remote computer must provide a compatible service:
- Windows VNC — start a standards-compatible VNC server and allow its listening TCP port through Windows Firewall for your local subnet.
- Mac VNC — enable macOS Screen Sharing or Remote Management and allow the intended user.
- Linux VNC — start a compatible RFB/VNC server for the desktop session you want to share.
- Windows RDP — enable Remote Desktop on a supported Windows edition and allow TCP port 3389 on the intended network.
A QuickRemote companion application is not required for a standard VNC, macOS Screen Sharing, or Windows RDP endpoint. Optional QREX companion features are separate from the base VNC connection.
Create a Connection
- Open QuickRemote and select New Connection.
- Choose VNC or, when available on this platform, RDP.
- Enter the host name or IP address and port. The common defaults are VNC
5900and RDP3389. - For VNC, enter the server password or leave it blank when the server explicitly allows No Authentication.
- For RDP, enter the Windows account name and password in the RDP credential form.
- Select Connect. Save the profile if you want to reuse it.
A blank VNC password does not bypass server security. QuickRemote can submit an empty value only so a server configured for No Authentication can complete its normal RFB negotiation. If the server requires a password, enter the password configured on that server.
VNC Viewing and Control
Input modes
| Mode | Behavior | Best for |
|---|---|---|
| Pointer | Move the remote cursor like a trackpad, then tap or click. | Small desktop controls and precise work. |
| Touch | Send the pointer directly to the touched position. | Large controls and quick navigation. |
- Drag with one finger or the mouse to move the pointer.
- Use the right-click gesture or mouse secondary button for context menus.
- Use two-finger scrolling and pinch zoom on touch devices.
- Open the extended keyboard for modifiers, Escape, Tab, arrows, and function keys.
Display modes
- Fit — fit the full remote desktop into the available area.
- Native — display the remote pixels at their natural scale where possible.
- Percentage — choose a custom scale for readability or workspace size.
Performance modes
Start with Auto on a local network. QuickRemote keeps one framebuffer request outstanding, paces follow-up updates, and displays immediate local cursor feedback so input does not wait for the next server-rendered frame.
- Use a smoother/high-speed mode on a reliable wired or fast Wi-Fi LAN.
- Use a lower-bandwidth mode when the connection is unstable or the server encodes frames slowly.
- Reducing color depth can help older servers, but prefer the default first.
QuickRemote can reconnect after a temporary network interruption. If the server accepts only one viewer, wait briefly before reconnecting so the previous server-side session can close.
RDP Connections
Mac
After entering the Windows credentials, choose:
- Open in QuickRemote — use the built-in RDP display and input window.
- Open in another RDP app — hand a temporary profile to an installed RDP application. QuickRemote does not place the password in the temporary profile.
iPad
RDP opens inside QuickRemote. You can connect, use pointer and Unicode input, place the app in the background, return to the session, disconnect, and reconnect.
Windows
QuickRemote saves the endpoint and opens Windows Remote Desktop (mstsc). Authentication prompts and the resulting RDP session belong to that Windows application.
Current RDP boundary
QuickRemote does not currently advertise RDP audio, RDP clipboard synchronization, drive, printer, smart-card, USB, camera, serial-device redirection, or RDP-over-SSH as built-in features. The Audio setting in QuickRemote is for an optional compatible QREX VNC host and does not enable RDP audio.
LAN Discovery and Wake-on-LAN
- Open LAN Discovery to browse mDNS/Bonjour advertisements and scan common VNC/RDP ports on the local subnet.
- Select a result to prefill a connection profile, then review the protocol and port before connecting.
- If discovery finds nothing, create a manual profile using the target IP address.
- For Wake-on-LAN, save the target MAC address and ensure the remote computer and network support wake packets.
Guest Wi-Fi, client isolation, VLANs, VPN routing, and different subnets can prevent discovery even when manual connection works.
Optional VNC SSH Tunnel
SSH tunnelling is available for VNC profiles. Configure the SSH host and authentication details in the profile, then connect to the VNC endpoint through that tunnel.
The SSH tunnel setting does not apply to RDP. Keep direct VNC working before adding a tunnel so server and tunnel problems can be diagnosed separately.
Troubleshooting
| Symptom | What to check |
|---|---|
| Connect is unavailable with an empty VNC password | Use the current QuickRemote build. The password field may be blank; host and port must still be valid. |
| Authentication fails | Confirm whether the VNC server allows No Authentication or requires its configured VNC password. For RDP, confirm the Windows account format and password. |
| Connected, but the first frame never appears | If QuickRemote reports Connected or the port accepts TCP, the port is not simply closed. Check the VNC server capture method, selected desktop/session, service permissions, and whether an independent VNC viewer also receives a frame. |
| Black Windows VNC screen | Restart the VNC service after changing its security or capture settings. Verify that service mode can capture the active desktop and test the same endpoint with another viewer. |
| Mac Screen Sharing does not connect | Confirm Screen Sharing is enabled, the intended macOS user is allowed, and no stale single-viewer session is still active. |
| Pointer feels delayed | Use Auto or the smooth LAN mode, check the FPS/latency display, and compare with a wired or less congested network. Server-side capture/encoding speed can still limit visible frames. |
| Discovery finds no devices | Try a manual IP connection and check guest-network isolation, VLANs, VPN routes, and local-network permissions. |
| Windows RDP does not open inside QuickRemote | This is expected on Windows: QuickRemote launches mstsc. Built-in RDP is provided on Mac and iPad in this release. |
Credentials and Privacy
- QuickRemote does not require a relay account for direct LAN connections.
- Saved credentials use the operating system's secure storage.
- Connection profiles, discovery results, and session statistics remain on your device.
- Remote screen data and input travel directly between QuickRemote and the endpoint or tunnel you configure.
- Use remote computers only when you have authorization to view and control them.