High Volume Photo Storage: 90TB Studio Math for Photographers

High Volume Photo Storage: 90TB Studio Math for Photographers

For most photographers with large, growing libraries, the safest practical approach is a hybrid workflow: fast local working storage, a redundant NAS, a cloud copy offsite, and an offline archive. Start by calculating how many terabytes you add each year, because that number decides which plan or hardware fits. The rest of this article covers file formats, workflows, and how to choose.

---

TL;DR:

• Estimate annual growth from files retained and actual average file sizes, then multiply the working set by 1.5 to 2 for edits, exports, and versions.
• Keep RAW or lossless TIFF as masters, export JPEG, HEIC, or AVIF as derivatives, and never overwrite a master with a repeatedly saved lossy file.
• Keep three copies across two media types, with one offsite; RAID 6 can survive two simultaneous drive failures but cannot undo deletion or ransomware.
• Before clearing a memory card, confirm files open from two separate destinations; schedule nightly NAS sync, weekly cloud sync, and quarterly offline archiving.
• Budget for bulk cloud uploads that can take weeks on home connections, and test restoring a full project before relying on the service.

---

PhotoViewKeep Your Finished Work OrganizedPhotoView helps photographers curate finished photos and videos, publish portfolio galleries, and manage website embeds from one dashboard.Explore PhotoView

Table of Contents

• How do you estimate how much storage you need?
• Which file formats should you keep as masters?
• How do cloud, NAS, external drives, and tape compare?
• How do you apply the 3-2-1 rule to a large library?
• What should you look for in a scalable cloud strategy?
• How should storage fit your workflow?
• How do you keep files secure, organized, and preserved?
• What is a practical archiving checklist for the long term?
• Why does our author recommend this approach?
• How should you grow from hobbyist to studio storage?
• PhotoView: storage and presentation for photographers
• FAQ
• Sources

How do you estimate how much storage you need?

“High volume” is not a fixed number. It means your library grows faster than a single drive or a casual cloud plan can comfortably absorb. The fastest way to find out where you stand is to run the math on your own shooting schedule.

Take a working example. A studio producing 12 shoots a month at 200GB each needs roughly 28.8TB a year. Add scratch space, gallery builds, and exports, and that climbs to about 45TB a year, which means roughly 90TB within two years. Most photographers shoot less than that, but the method scales down cleanly.

File size drives everything. Full-frame RAW files from modern cameras range from 22MB to 100MB per image, depending on compression, and a JPEG of the same resolution is typically about one tenth of that. A 2,000-frame wedding in RAW can land anywhere between roughly 44GB and 200GB before you touch a single edit.

Then add overhead. Edits, exports, proofing galleries, and versioned copies all take room. As a planning rule, multiply your working set by 1.5 to 2 to cover them. Your raw ingest is the floor, not the total.

Use this checklist to compute your own number:

• Count your shoots per month, including personal and test work.
• Estimate files kept per shoot after culling, not files shot.
• Use your camera’s real average file size, not the maximum.
• Decide your retention policy: keep everything, or purge rejects after a set period.
• Apply a growth rate. If you are adding clients or moving to higher-resolution bodies, plan for 20 to 30 percent more each year.
• Multiply by 1.5 to 2 for edits, exports, and versions.

Write the result down as terabytes per year. That single figure makes every later decision easier, from picking a cloud tier to sizing a NAS.

Which file formats should you keep as masters?

The format you choose for your masters sets the floor for your storage bill. Image storage generally follows three philosophies: uncompressed, lossless, and lossy. RAW and lossless formats keep the most data. JPEG and newer lossy formats trade some of that data for far smaller files.

RAW masters are large because they hold the full sensor data, which is what gives you room to recover highlights and shift white balance later. That is the reason to keep them. A JPEG is efficient for delivery but is a poor candidate for repeated editing, since each re-save discards a little more information.

Image storage choices fall into uncompressed, lossless, and lossy philosophies: RAW and lossless formats preserve the most data, while JPEG and modern lossy formats trade quality for much smaller files. That trade is exactly why masters and deliverables should live in different formats.

Here is how to split the work:

• Masters: keep RAW, or lossless TIFF for flattened composites. These are your source of truth.
• Client deliverables: export JPEG for broad compatibility, or HEIC and AVIF where your clients’ devices support them and file size matters.
• Web and proofing copies: use the smallest acceptable lossy export, since you can always regenerate it from the master.
• Working edits: keep sidecar or catalog data rather than saving a full-resolution copy for every tweak.

Modern efficient formats such as HEIC and AVIF can shrink delivery files noticeably, which helps when you hold thousands of client galleries. They are best treated as derivatives. Compression decisions you cannot undo should never touch the only copy of a frame.

The rule that saves the most space over time is simple: maintain a single lossless master, never re-save a lossy file on top of itself, and keep derived versions only for clients who need them. Photographers who export a fresh JPEG for every request, without tracking them, quietly double their library in a year.

One more practical point: do not convert your RAW archive to another format just to save room unless you have tested the result against your editing software. Vendor RAW files stay readable as long as converters support them, and many photographers also store an open lossless copy alongside as insurance. Storage is the cheaper problem to solve.

How do cloud, NAS, external drives, and tape compare?

Each storage type earns a different job in your stack. The mistake is asking one of them to do all of them.

Cloud storage gives you scalability, an offsite copy, remote access, and often AI-powered search. Reviewers who test these services look for automatic uploads from phone and camera, smart search, and editing-tool integration, and practitioner testing also highlights fast uploads, version history, and Lightroom integration. The costs are bandwidth for the first bulk upload, a recurring subscription, and per-GB pricing that rises with your library.

A NAS (network-attached storage) is your fast, on-site home for the working set and recent archive. For professional, high-volume workflows, a server-grade NAS running RAID 6 is the recommended setup, because RAID 6 survives the simultaneous failure of two drives. There is a catch worth planning for: large drives of 16TB and up have long rebuild times, which raises risk while the array repairs itself. Buy drives from different batches and keep a spare on the shelf.

External drives and SSDs are ideal for transport, on-location backup, and short-term copies. Larger-capacity external drives are useful for backup, but institutions advise keeping multiple copies on different media types and in separate locations. A single drive in a desk drawer is not a backup strategy. Hardware options are easy to browse at retailers such as Best Buy’s picture data storage listings.

Tape and other cold storage suits very large archives you rarely open. It is slower to access and needs a drive and a process, so it fits studios with tens of terabytes of finished work that must be kept but seldom retrieved.

How the pieces fit:

• Local SSD or fast NAS: the working set, where speed matters.
• NAS with RAID 6: the on-site archive and first line of redundancy.
• Cloud: the offsite copy and remote access.
• Offline drive or tape: the last-resort archive you can lock away.

The hybrid model wins for most photographers because it combines local speed with cloud redundancy. You edit against fast disks, protect against hardware failure with RAID, and protect against fire, theft, or flood with an offsite copy. No single option covers all three.

Think about failure modes, not features. A NAS protects against a dead drive but not a burglary. Cloud protects against a burglary but not a slow connection on deadline day. An offline drive protects against an account lockout or accidental deletion that syncs everywhere. Layering them means each weakness is covered by another layer’s strength, and that is the entire logic of the stack.

How do you apply the 3-2-1 rule to a large library?

The 3-2-1 rule is the standard answer: keep three copies of your data, on two different types of media, with one copy offsite. Professionals commonly follow a 3-2-1 approach, and preservation guidance backs the same instinct: save copies on at least two different storage media stored separately.

For a photographer, that translates into something concrete:

1. Copy one: the working drive or fast NAS volume holding the live project.
2. Copy two: a NAS snapshot or a second local drive, on a different device from copy one.
3. Copy three: a cloud copy in a separate geographic location.
4. Optional fourth layer: an offline drive or tape that never touches the network.

Media diversity matters because identical drives from the same batch tend to fail in similar ways. Geographic separation matters because a flood or fire takes out everything in one building at once.

For multi-drive NAS units, consider RAID 6 and remember that RAID is not a backup. It keeps a failed drive from taking your files down, but it will not save you from deletion, corruption, or ransomware that syncs across the array. That is the job of snapshots and the offsite copy.

A cadence you can actually keep:

• Daily: import and cull straight from the card to two destinations.
• Nightly: automatic local sync from the working drive to the NAS.
• Weekly: cloud sync of finished and in-progress projects.
• Quarterly: a snapshot of completed work to the offline archive.

Pro Tip: Do not clear a memory card until the files exist in two separate places and you have opened a few to confirm they are readable.

What should you look for in a scalable cloud strategy?

Choosing cloud storage is mostly about cost shape, bandwidth, and fit with your editing tools. Leave brand names aside until you know what you need.

Start with pricing shapes. Per-GB subscriptions scale smoothly but grow expensive at high capacity. Tiered plans bundle storage in steps, which is cheaper when your library fits a tier neatly and wasteful when it does not. Custom or enterprise pricing becomes worth a conversation once you cross into the tens of terabytes. To estimate monthly cost, take your terabytes per year from the first section, project two years out, and price the tier that covers that number with a margin.

Plan the upload before you sign up. Your first bulk upload, often called seeding, can take weeks on a typical home connection. Ongoing sync can be throttled, and APIs may limit how fast you can push files. Calculate it: a large library on a slow upstream link is a long job, so schedule it in batches rather than expecting it to finish quickly.

Check integration priorities against how you work:

• Lightroom publishing, so finished selections flow out without manual exports.
• Automatic mobile import, so phone captures reach the library.
• API or S3 compatibility, if you want to script backups or connect other tools.
• Smart search and AI tagging, which pay off once you hold tens of thousands of images.

Then read the operational fine print:

• Versioning limits: how many prior versions are kept, and for how long.
• Retention policies: what happens to deleted files and how long you can recover them.
• Restore speed: how quickly you can pull a large gallery back down, which matters most on the day something goes wrong.
• Exit path: whether you can export everything in original formats if you leave.

A good cloud strategy is one you could restore from under pressure, not just upload to on a calm afternoon. Test a restore of one full project before you trust the plan. You will learn more from that single test than from any feature list.

How should storage fit your workflow?

Storage layout should follow the stages of a job: ingest, working set, archive, and delivery. The right balance depends on what kind of work you do.

Wedding photographers need fast turnaround. Ingest to two destinations on the day, keep the working set on a local SSD, and push proofs to a client gallery quickly. Archive the finished set within days, since new bookings arrive every weekend.

Commercial photographers handle large masters and many revisions. Keep the working set on a fast NAS so an art director’s change request does not mean hunting across drives, and track versions carefully because files multiply with every round of feedback.

Studio photographers shoot in controlled environments and often produce large batches in a single session. Tethered capture straight to a fast volume, with an immediate mirror to the NAS, protects a full day’s output.

Whichever template fits, the stages stay the same:

1. Ingest to two separate destinations before you clear any card.
2. Cull and rate on the working volume, discarding rejects early to save space.
3. Edit against the working set on local SSD or fast NAS.
4. Export derivatives for delivery and keep them apart from masters.
5. Move finished work to the archive tier, with a cloud copy and an offline copy.

Where things live matters. Keep the working set local and fast. Keep the archive in the cloud or cold storage, where capacity is cheap and speed matters less. Keep deliverables in a folder structure that separates them clearly from masters.

Automation reduces mistakes. Smart Folders can group images by rules instead of manual dragging, automated imports pull in phone shots without a cable, and Lightroom publishing sends selections where they need to go. Our guide to mobile photo import shows how the phone roll fits in, and our walkthrough on curating from Lightroom to the web covers the publishing side. Fewer manual steps means fewer files that end up in only one place.

How do you keep files secure, organized, and preserved?

Protection is part technology and part habit. Start with the basics: encrypt data at rest and in transit, use private sharing controls, and avoid accidental public exposure. A public link left active is a common leak, which is why we wrote about the public link risk for photographers and about four security priorities for cloud storage. If you share work privately with clients or collaborators, Alloquy’s piece on showing proof without exposure is a useful companion read.

Physical media needs care too. Preservation guidance recommends cool, stable, relatively dry storage, about 30 to 50 percent relative humidity and 70°F or below. The Library of Congress also advises keeping storage media away from basements, attics, and radiators, where humidity and temperature swing the most.

Recommended storage conditions: about 30–50% relative humidity and 70°F or below, using photo-safe enclosures that meet ISO 18902.

Good habits that keep a library usable:

• Embed EXIF, IPTC, and XMP metadata so captions, credits, and rights travel with the file.
• Adopt one consistent naming convention, such as date plus client plus sequence, and never change it midstream.
• Generate checksums when you archive a project, then re-check them periodically to catch silent corruption.
• Refresh archive media on a schedule: preservation guidance suggests migrating saved copies to current media about every five years.

Metadata is also a search tool. With a large library, consistent keywords and captions are the difference between finding a frame in seconds and scrolling for an hour.

What is a practical archiving checklist for the long term?

Archiving works best when you decide in advance how long each project stays where. Sort finished work into retention bins:

• Short-term, 1 to 3 years: recent client work you may be asked to re-deliver. Keep it on the NAS and in the cloud.
• Mid-term, 3 to 7 years: older work with occasional demand. Move masters to cheaper cloud tiers or an offline drive.
• Long-term, 7 years and beyond: portfolio-level and legacy work you intend to preserve. Keep multiple copies on different media.

Run this checklist whenever a project closes:

• Verify master integrity with checksums before anything is deleted from the working volume.
• Store copies on at least two media types, such as cloud and an offline drive.
• Keep one copy in a separate geographic location from your studio.
• Record where each project lives, so you can find it years later.
• Put a reminder on the calendar to refresh media about every five years, following preservation guidance.

Know when to convert. If a file format is being abandoned by software, reformat masters before support disappears, and test the result. When you do convert, always work from the original, and avoid repeated lossy saves, since each one discards detail you cannot recover. A decade-scale archive is mostly the discipline of checking in on it before something fails.

Why does our author recommend this approach?

This guide comes from Mitch Russo, a writer who covers photography workflows and the storage choices behind them from the photographer’s side of the desk. The recommendations here lean on published preservation guidance and practitioner testing rather than on hardware hype, and we cite those sources where they apply.

Here is what we built into PhotoView so these workflows are easier to follow:

• Secure storage for finished photos and videos, kept organized alongside your portfolio.
• Lightroom publishing, so selections reach your site without repeated manual exports.
• Smart Folders that keep galleries current as your library grows.
• Private sharing for clients and collaborators, with control over who sees what.
• Live embeds that keep galleries on an external website updated from one dashboard.

If you want product-specific detail, our photo storage for photographers page explains how storage and presentation work together, and the security guide linked earlier covers private links and access control in depth.

How should you grow from hobbyist to studio storage?

Spend where it protects you, not where it merely feels fast. In my view, redundancy and offsite protection beat marginal speed gains every time, because a faster drive saves minutes while a lost library costs years.

Here is a staged path:

• First 5TB: an organized working SSD plus a cloud backup. Keep folders tidy from day one.
• 5TB to 25TB: add a NAS running RAID 6 and replicate it to the cloud.
• 25TB and beyond: consider custom enterprise cloud pricing or managed storage, where the economics change.

Do not buy hardware until you have calculated your real terabytes per year. Photographers routinely overbuy for a library they imagine, or underbuy for the one they actually have.

— Mitch Russo

PhotoView: storage and presentation for photographers

If you want one place that holds your finished images and presents them well, we built PhotoView for exactly that. We offer secure storage for finished photos and videos, Lightroom publishing, Smart Folders, private sharing, responsive portfolio templates, and live embeds that keep an existing website current. You update your work once, and it appears everywhere it is shown.

Our plans are tiered by storage. Starter is $3.99 per month or $39.99 per year, Growth is $5.99 per month or $59.99 per year, Studio is $7.99 per month or $79.99 per year, and Premier is $11.99 per month or $119.99 per year. Libraries beyond those tiers can use a Custom plan. Every plan includes all templates and portfolio features, so you pay for storage, not for design options.

Your next step is simple: take the terabyte number you calculated earlier, then check our photo storage plans to see how they fit your workflow.

FAQ

How much storage do 1,000 pictures take up?

It depends mostly on file type. Full-frame RAW files run from 22MB to 100MB each, so 1,000 RAW images can fill roughly 22GB to 100GB, while the JPEG versions are about one tenth of that size.

What is the best way to get more storage for my pictures?

Add storage in layers rather than replacing one drive with a bigger one. A NAS with RAID 6 handles capacity and redundancy on site, and a cloud plan adds an offsite copy that grows as your library does.

Where can I find free image storage?

Many cloud services offer a small free tier, but free space fills quickly for anyone shooting RAW. Treat free storage as a trial or a supplement, and plan paid capacity for your master files.

What should I store photo backups on?

Use at least two media types, with one copy kept offsite. Preservation guidance recommends saving copies on two different storage media stored separately, which in practice means a NAS or external drive plus a cloud copy.

Sources

• Google
• What is a RAW image file and how much memory does it require? | Sony USA
• File formats and compression — Computational Photography

Recommended

• 4 Security Priorities for Photographers’ Cloud Storage
• Protect Photos Online: The Public Link Risk for Photographers
• 3 Private Photo Sharing Workflows to Speed Delivery for Photographers