QNAP's remote access features let video editors share footage previews, portfolio content, and client deliverables directly from their NAS. Without uploading to Frame.io, Dropbox, or WeTransfer. For Australian editors dealing with NBN upload speeds, this changes the equation significantly: instead of waiting hours to upload 4K files to a third-party service, your NAS becomes the delivery platform. This guide walks through exactly how to set it up and what to realistically expect from your connection.
In short: QNAP remote access via myQNAPcloud works well for client approvals, portfolio sharing, and remote file browsing. It won't replace your NAS for remote editing over the internet. AU NBN upload speeds make live remote editing impractical for high-bitrate footage. Use it as a client-facing tool, not a remote office solution.
The Australian upload speed problem nobody talks about honestly
Before getting into QNAP setup, it's worth being direct about what remote access can and can't do in Australia. A typical NBN 100 connection delivers around 56-80 Mbps upload. An NBN 250 plan does better at 80-100 Mbps. That sounds substantial until you look at what your footage actually requires:
- H.264 4K at 200 Mbps: your 80 Mbps upload is already insufficient for live remote playback
- ProRes 422 4K: ~1,485 Mbps. Completely impractical over any consumer NBN connection
- BRAW 4K at Q3 quality: ~300 Mbps. Still exceeds typical AU upload speeds
This isn't a QNAP limitation. It's NBN. No remote access software in the world can push 1,485 Mbps through an 80 Mbps pipe. If you've read US-based NAS content that suggests using your NAS for "remote editing over the internet," that content was written for markets with symmetric gigabit fibre where 1,000 Mbps upload is common. Australia is not that market.
What QNAP remote access is genuinely good for: H.264 proxies, compressed client review files (720p or 1080p H.264 at 50-100 Mbps), deliverables your client just needs to download once, and remote file management where you're browsing and copying files rather than streaming them live.
CGNAT: the access blocker many NBN users don't know about
There's a second complication unique to the Australian market: CGNAT (Carrier-Grade NAT). Many NBN providers put residential and small-business customers behind CGNAT, which means your connection does not have a dedicated public IP address. Multiple customers share a single IP, and inbound connections to your NAS from the internet are blocked by the carrier's network.
CGNAT affects remote access in two ways: it prevents standard port-forwarding setups from working, and it may cause myQNAPcloud relay connections to time out under heavy load. Affected ISPs include some Aussie Broadband plans on HFC, some Superloop plans, and several smaller ISPs. If you've set up port forwarding on your router but still can't reach your NAS remotely, CGNAT is the most likely cause.
Fixes:
- Request a static IP from your ISP. Most AU ISPs offer this for $5-$15/month. This gives you a dedicated public IP and bypasses CGNAT entirely.
- Use myQNAPcloud relay. QNAP's cloud relay service tunnels connections through QNAP's servers, bypassing CGNAT. This works even without a public IP, but adds latency and speed is capped by the relay.
- Use Tailscale. A modern VPN alternative that uses NAT traversal to connect devices peer-to-peer regardless of CGNAT. Free tier covers small setups. Works reliably on QNAP without requiring a static IP or port forwarding. This is the cleanest solution for most editors.
Setting up myQNAPcloud for client access
myQNAPcloud is QNAP's built-in remote access service. It gives your NAS a fixed internet address (e.g. yourstudio.myqnapcloud.com) and handles the relay if you're behind CGNAT. Here's the full setup process:
Step 1: Create a myQNAPcloud account and register your NAS
Open QTS on your QNAP and launch the myQNAPcloud app from the App Center (if not already installed, download it from the QNAP App Center. It's free). Sign in with your QNAP ID, or create one at account.qnap.com. Once logged in, register your NAS with a unique device name. This becomes your remote address. Choose something professional if clients will see it: smithstudio or brightonediting rather than qnap-nas-12345.
Step 2: Configure access control
In the myQNAPcloud app, set your device visibility to Private (not Public). Private means only authenticated users can access the NAS remotely. Public would expose it to anyone who knows the address. Under Access Control, create a dedicated user account for client access with restricted permissions: read-only access to a specific shared folder (e.g. a "Client Previews" share), no access to any other folder, and no ability to modify or delete files.
Never give clients (or anyone who doesn't need it) access to your full NAS. Segment client access to a single shared folder that contains only the files you explicitly place there.
Step 3: Enable HTTPS and set a strong password
In QTS, go to Control Panel → Network & File Services → myQNAPcloud Link and ensure HTTPS is enabled. QNAP provides a free SSL certificate via myQNAPcloud. Enable it. This encrypts the connection between your client's browser and your NAS. Without HTTPS, any file your client downloads or previews over a public connection is transmitted in plaintext.
Set a strong password on the client user account. At minimum 12 characters with mixed case and numbers. Consider enabling two-factor authentication (2FA) on the account in QTS Control Panel → Users if your NAS model supports it.
Step 4: Prepare the client preview folder
Create a shared folder in QTS called "Client Previews" or similar. This is the only folder clients ever see. Your workflow for sharing a job:
- Export a compressed H.264 or H.265 review copy of the cut (1080p, 20-50 Mbps. Manageable over NBN)
- Place it in the Client Previews folder inside a subfolder named after the project or client
- Share the myQNAPcloud link and the client's login credentials
- Client browses to the link, logs in, downloads or streams the review file
- After approval, delete the review copy or archive it. Don't leave client files accumulating in the preview folder
For final deliverables (the full-res exported file), the same workflow applies but the file is larger. AU upload speeds can turn a 50 GB ProRes master into a multi-hour upload to a third-party service. From your NAS, the client downloads at their own speed directly from the file sitting on your local drives.
Tailscale: the better solution for remote editing access
If you want to access your NAS remotely for file management (browsing, moving, backing up projects) rather than client sharing, Tailscale is a cleaner solution than myQNAPcloud for personal use.
Tailscale creates an encrypted peer-to-peer VPN between your devices. Your Mac on location, your NAS at the studio. Without requiring port forwarding, static IP, or CGNAT workarounds. It uses NAT traversal to connect devices regardless of what's between them. The free tier supports up to 100 devices on a personal account, which covers most small studios.
Installation on QNAP: open the App Center and search for Tailscale. Install the official Tailscale container app. Log in with your Tailscale account. Your NAS appears in your Tailscale network as a device with a stable private IP address (usually 100.x.x.x). From any Mac or iOS device logged into the same Tailscale network, you can mount the NAS via SMB as if it were on your local network. No public IP, no port forwarding, no CGNAT issue.
The catch: Tailscale is for your devices and trusted team members, not for anonymous client access. For sharing files with external clients, myQNAPcloud or a dedicated file-sharing method is still the right approach.
QNAP File Station: what clients actually see
When a client accesses your NAS via myQNAPcloud, they interact with QNAP's File Station. A web-based file browser. It works in any modern browser without requiring your client to install anything. From File Station, clients can browse folders, preview images, stream video files (H.264 and H.265 playback works natively in most browsers; ProRes will require download), and download files directly to their machine.
For clients who need a simpler experience, QNAP's Qfile mobile app provides a cleaner interface on iPhone and Android. They browse your shared folder and download directly to their device. The setup on your end is identical; you just share the myQNAPcloud link and their login details.
This positions your NAS as infrastructure that earns its cost. Instead of paying $15-$50/month for Frame.io or Dropbox Business to handle client review and delivery, the NAS you've already paid for handles it. Over a 3-year NAS lifecycle, that's $540-$1,800 in subscription costs that stay in your pocket.
What this realistically means for AU video editors
Remote access won't turn your home NAS into a cloud editing suite. But it will:
- Eliminate Dropbox/WeTransfer/Frame.io fees for client review and delivery on compressed files
- Give you a professional-looking URL to share with clients instead of a temporary upload link
- Let you access your NAS files from location shoots, client sites, and offsite work. For file management and download, not live high-res editing
- Enable your NAS to serve as a self-hosted portfolio platform for high-resolution work samples
The NBN upload speed constraint is real, but it mostly affects live streaming of high-bitrate footage. For everything else. Download-based client review, file delivery, portfolio hosting, remote file management. It's a meaningful capability that replaces paid subscriptions with infrastructure you already own.
For more on how the NAS fits into the broader storage architecture for creative professionals. How hot NVMe cache, warm SATA SSDs, and cold HDD storage work together. See the hot vs cold storage guide. For connectivity decisions (Thunderbolt vs 10GbE), see the connection speed comparison.
Charging clients for data retention? If you store delivered footage for clients under contract data retention clauses, the NAS you've set up for remote access can also serve as the storage infrastructure for a billable data retention service. See the data retention guide for how AU editors are building this into their client quotes as a revenue line item.
Our NBN Remote Access Reality Checker checks whether your NBN plan supports the direct port-forwarding that QNAP relies on, or whether myQNAPcloud relay is the more reliable path.
Related reading: our NAS buyer's guide, our Synology vs QNAP comparison, and our remote access and VPN guide.
Can I edit footage remotely over my NAS internet connection?
Not practically, for most AU editors. Live remote editing requires the NAS to stream footage to your remote machine in real time. ProRes 4K HQ requires around 186 MB/s sustained; NBN 100 uploads typically reach 7-10 MB/s. That's a 20x gap. What works: editing with proxy files (H.264 at 8-20 Mbps) where the remote machine has a local proxy copy and syncs back to the NAS when you reconnect. Some editors use this workflow effectively for travel edits where only the proxy is worked on remotely and the full-res grade happens back at the studio. For a true remote editing solution, look at cloud editing platforms (Evercast, Frame.io, Sohonet) which are purpose-built for it and route traffic through datacentres with fast uplinks. Not your NBN connection.
Is myQNAPcloud secure enough for sharing client footage?
Yes, with proper configuration. The key requirements: enable HTTPS with QNAP's SSL certificate, set client accounts to Private (not Public), limit client permissions to read-only access on a dedicated shared folder, use strong passwords, and enable 2FA if supported on your NAS model. With these settings, myQNAPcloud is more secure than emailing download links and comparable to standard consumer file-sharing services. The weak point is usually password hygiene. Don't reuse passwords or share credentials over insecure channels (SMS is fine; unencrypted email is not ideal). QNAP's servers handle the relay; files are not stored on QNAP's infrastructure, they stream from your NAS.
My ISP uses CGNAT. Will remote access still work?
Yes, with the right approach. Standard port forwarding won't work behind CGNAT. Your options: (1) use myQNAPcloud's relay service, which routes traffic through QNAP's servers and doesn't require a public IP. This works behind CGNAT but adds latency; (2) install Tailscale on the QNAP and your other devices for personal access. Tailscale uses NAT traversal that bypasses CGNAT; (3) pay your ISP for a static IP ($5-$15/month typical in AU) which removes CGNAT for your connection. If you're unsure whether you're on CGNAT, check your router's WAN IP address against your public IP (visit whatismyip.com). If they differ, you're behind CGNAT.
Can clients preview video in their browser, or do they have to download it?
H.264 and H.265 files stream in most modern browsers without downloading. QNAP's File Station includes a built-in video player that handles these formats. ProRes files are not natively supported in browsers and will require download. For client review, export a 1080p H.264 review copy for browser streaming and include the full-res master in the same folder for download when approved. This gives clients a fast, friction-free preview experience while the full deliverable is ready when they need it.
How is this different from just using Dropbox or Google Drive?
The core difference is where files live. With Dropbox or Google Drive, you upload files to their servers. You pay monthly for storage, upload time is limited by your NBN upload speed, and you're dependent on their service availability. With your NAS, files stay on your hardware. There's no upload step for the initial transfer (files go directly to the NAS from your editing machine on your local network). You pay once for storage capacity rather than monthly for cloud storage. The trade-off: cloud services have faster download speeds globally because they run from datacentres; your NAS downloads depend on your NBN upload speed. For high-volume deliveries to international clients, cloud services have an edge. For AU-based clients and standard review workflows, NAS-based sharing is economically compelling.
Do I need a static IP address to use QNAP remote access?
No. MyQNAPcloud assigns your NAS a stable hostname (yourstudio.myqnapcloud.com) and handles address changes automatically via DDNS. If your home or studio IP changes (which it will on most NBN connections), myQNAPcloud updates the DNS record automatically. You only need a static IP if you want to bypass the myQNAPcloud relay entirely and use direct port-forwarding. Which is faster but requires both a static IP and that you're not behind CGNAT. For most editors, myQNAPcloud relay or Tailscale is simpler and more reliable than managing port forwarding.
Getting the most out of your NAS starts with the right drives. Mixed or incompatible drives are the most common cause of NAS performance problems that remote access makes worse.
NAS Drive Compatibility Guide →