Digital media files have grown enormously, driven by high-resolution sensors, uncompressed raw data, and the demand for high dynamic range. Every frame now carries extensive metadata and integrated data, often reaching tens or hundreds of megabytes. With rising resolutions and accelerating frame rates, the real question isn’t which camera to buy — it’s how we manage storage after the fact.
NAS systems have been the backbone for professional photography workflow, but today they are starting to look like transitional tech. Cloud-native file systems, first-party storage gateways, and hybrid caches are blurring the lines between local and remote storage. Instead of maintaining RAID arrays and constantly swapping failed disks, creators can now mount petabyte-scale cloud storage directly onto their desktop. It’s not science fiction. It’s quietly becoming the norm.
Local SSDs, a big NAS at home, and cloud backup are safe and reliable but not durable. This stack is starting to show cracks in the fast and mobile world.
The New Cloud-Native workflow
Looking beyond NAS boxes, cloud-mounted file systems and high-performance storage gateway solutions let you work on assets that live primarily off your machine — sometimes even off your studio network.
AWS Storage Gateway
AWS File Gateway is a strong hybrid solution that exposes Amazon S3 as an on-premises SMB/NFS share. Adobe applications treat it like any other network share. It works well as an archive tier, but it is not good for a primary creative workspace.
Works Well for:
- Storing raw files, Lightroom catalogs, or exported assets
- Lightroom Classic archives
- Photoshop PSB/PSD files
- Illustrator files
- Photo libraries that are not actively edited by multiple users
Not Ideal for:
- Premiere Pro or After Effects real-time editing
- Scratch disks
- Large PSB files (> 10 GB) opened repeatedly, which adds latency
Storage Gateway has ~20–40 ms latency plus cloud round trips. High-demand, random-access applications like Premiere Pro or After Effects need sub-millisecond I/O for smooth playback and scrubbing.
Azure File Share / Azure File Sync
These are supported as network drives. They are fully compatible with Adobe I/O operations, but performance depends heavily on local cache configuration. Azure File Sync adds a local Windows Server cache, which gives much better performance than an SMB-only network drive.
Works Well for:
- Lightroom catalogs
- Photoshop documents
- Premiere projects that can read media, though scrubbing is not smooth unless it is locally cached
This is the most mature first-party option if you want something close to “NAS in Cloud.”
Google Cloud Storage (GCS) Fuse
Google’s Cloud Storage FUSE (often referred to as GCS FUSE) is better in its 2024 and later releases. Cloud Storage FUSE now mounts Google Cloud Storage buckets as POSIX file systems, making it useful for ingest, archiving, and backup workflows. It delivers faster metadata performance and far better caching. However, it is still not fast enough for active Adobe editing—random access on large project files remains an issue, and apps like Premiere Pro and After Effects can drop frames or struggle with seek times.
Works Well for:
- Lightroom photo storage (not catalog)
- Photoshop file storage
- Raw archive
- Syncing output files to the cloud
Think of Cloud Storage FUSE as a cold-tier storage that can act like a file system — not a workspace for heavy editing.
There is growing technology that bridges Adobe tools and cloud object storage via gateway-like mechanisms. The Wasabi–Adobe integration is probably the most production-ready for creatives right now. For more ambitious workflows (especially hybrid teams or very large media), LucidLink and CentreStack are very promising. And in the research space, Objcache hints at what future storage-gateway architectures could look like. (LucidLink)
Of course, the tech is always evolving:
- Amazon S3 Express One Zone + Mountpoint for Amazon S3: S3 Express One Zone is no longer just cold storage. With Mountpoint for Amazon S3, you can mount buckets like a local drive and open raws with surprisingly low latency. This is great for sequential reads, but not ready for giant PSB files or heavy video scratch.
- Google Cloud Storage — Cloud Storage FUSE v2: Google’s rewritten Cloud Storage FUSE dramatically cuts metadata lag and round-trip overhead. Browsing large folders feels faster, and partial-file reads are smarter. It is still not built for intensive editing, but it is improving quickly.
- Azure Elastic SAN + Premium File Shares: Microsoft is pushing for true cloud-native NAS behavior through SMB Direct, RDMA, and high-performance file shares. This is the closest thing to a cloud-native file system that Adobe applications can actually edit from without falling apart, though it is still slower than local NVMe.
NAS still has a place in a professional workflow, but its limitations are becoming impossible to ignore — you can’t use it as a true scratch disk for Adobe apps, and performance caps haven’t moved in years. The more realistic future isn’t bigger RAID arrays, but Adobe eventually partnering with cloud providers to remove these bottlenecks instead of pouring all its energy into AI features nobody asked for.
At some point, the trade-offs won’t matter. Cloud-native storage already offers near-eleven-nines durability and geo-redundancy, which means you no longer need a second NAS sitting in a friend’s basement as disaster insurance. We’re not fully there yet, but the direction is obvious: local storage is becoming temporary, and the cloud is quietly becoming the real solution.
The next time you’re about to expand your NAS, ask yourself: Is this still a sustainable strategy, or just a habit we haven’t questioned yet?
