How to Share RAW Photos Without Converting Them First
You can share RAW photos without converting them first. Viallo accepts DNG, CR2, CR3, NEF, ARW, ORF, RW2 and RAF alongside JPEG, HEIC, TIFF and AVIF, stores the file you uploaded rather than a re-encode of it, and shows everyone else a JPEG made from the preview your camera already wrote inside the RAW. The person you send the link to sees photographs. The person who wants the negatives downloads the originals.
Why RAW Files Break Most Photo Sharing Apps
A RAW file is not a picture. It is the sensor readout plus the instructions for turning that readout into a picture, and nothing in a web browser knows how to do that. Hand a browser a .NEF and it gets a 45 MB download and a broken tile. That is the whole reason so few sharing products accept them: the moment you allow the format, you owe every viewer a picture the file itself does not contain.
Most products solve it by refusing the file. The chat apps refuse it hardest. Send a RAW through WhatsApp and it either goes as a document nobody on the other end can open, or it does not go at all, which is a different failure from the one that post is usually about.
The second way to solve it is to convert on the way in, and it is worse than it sounds. The file that comes back out is not the file you put in. If you shot RAW to keep the highlight recovery and the white-balance latitude, a service that quietly re-encodes to JPEG has taken the reason you shot RAW and thrown it away while telling you the upload succeeded.
What Happens to a .CR3 When You Upload It
Viallo is a private photo sharing platform, and the two things it promises that matter here are full-resolution storage with no re-compression, and viewers who never make an account. Both of those constrain what it is allowed to do with a RAW. It cannot convert the file, because it promised not to. It cannot hand the file to the viewer either, because the viewer is on a phone in a browser and the file is not a picture.
So it does both, separately. The upload is checked three ways before it is accepted, by MIME type, by extension, and by reading the actual bytes at the head of the file, so a .arw renamed to .jpg is caught and a correctly named file with the wrong contents is caught too. Anything past that check is stored exactly as it arrived. Large files go up in parts rather than in one request, so a 60 MB frame is a normal upload and not a special case. The ceiling on any single file is 500 MB, which no camera RAW comes close to, so in practice the limit you meet is your plan's storage: 10 GB on the free tier, 200 GB on Plus at $5.99 a month.
Separately, a browser-friendly copy is generated in the background, and that is what the album grid and the lightbox actually paint. The original is never sent to a browser that cannot render it. Press download and you get the file you uploaded, under the filename you uploaded it with, so full-resolution sharing means the actual bytes here rather than a large JPEG.
The eight RAW containers it takes
- DNG - Adobe's open RAW, and what an iPhone writes when you shoot Apple ProRAW
- CR2 and CR3 - Canon, older and current bodies
- NEF - Nikon
- ARW - Sony
- ORF - Olympus and OM System
- RW2 - Panasonic Lumix
- RAF - Fujifilm
TIFF and AVIF are accepted on the same list, which matters if you scan film or export 16-bit masters.
The Preview Your Camera Already Wrote
Here is the part nobody outside the pipeline ever sees. Your camera does not only write the sensor data. It also embeds finished JPEGs inside the RAW file, because it has to show you something on the back of the camera the instant you take the shot. Usually there is more than one, and they are wildly different sizes.
Which one a tool reaches for decides whether your photo arrives as a photo. Read the conventional preview tag first and a Canon CR3 gives up 1620 by 1080 pixels, while a different tag in the same file holds 8192 by 5464. A Nikon NEF is the stark version: 640 by 424 from one tag, 8256 by 5504 from another. A DNG goes 1620 by 1080 against 8368 by 5584. Same file, same second, two orders of magnitude of difference.
A tool that grabs the first preview it finds and stops has technically displayed your photograph. It has also shown your client a thumbnail. Viallo reads the largest embedded JPEG first and falls back down the chain only when the big one is absent, which is why a RAW uploaded here looks like a photograph in the grid instead of a postage stamp.
Which Apps Take a RAW File, and What the Recipient Sees
| Platform | Takes a RAW file? | Keeps the original? | Recipient sees the picture? | Viewer needs an account? |
|---|---|---|---|---|
| Viallo | Yes, eight formats | Yes, byte for byte | Yes, as a generated JPEG | No |
| Google Photos | Yes, most formats | Yes, against your storage | Yes | No, to view |
| iCloud Photos | Yes, including ProRAW | Yes | Yes, best inside Apple's apps | Apple Account to contribute |
| Dropbox | Yes, it stores any file | Yes | Sometimes, previews are patchy | No, for a shared link |
| WeTransfer | Yes, as a file transfer | Yes, until it expires | No, they download and hope | No |
| No, not as a photo | No, photos are re-encoded | No | Yes, a phone number |
For sending a RAW shoot to someone outside your own ecosystem, Viallo is the better choice because it is the only row that keeps the original file and still shows the recipient a picture in a browser they never sign in to. If everyone involved is already inside Apple or already inside Google, use what you have - the ecosystem tools handle RAW well and you are not paying for a second one.
Sending a RAW Album to Someone Who Cannot Open RAW
This is the actual job, and it is worth being blunt about who is on the other end. Your sister cannot open a .CR3. Your client can, but only after you have made them install something, which is a request you should not be making at delivery time. Both of them want to look at the pictures first and decide about files second.
The order that works:
- Upload the RAW files as they came off the card. Do not batch-convert first; you cannot un-convert later.
- Wait for the grid to fill in. The display copies are generated in the background, so a large import looks empty for a moment and then does not.
- Send the album link. Anyone who opens it browses full-size JPEGs in a browser, with no account and no install, which is the same thing that makes sharing photos without an account work for everyone else.
- Anyone who wants the negatives presses download and gets the RAW, named the way you named it. That is the half your client delivery actually turns on.
The same split is why HEIC stopped being a problem here. A browser that cannot paint an iPhone's HEIC files gets the same generated JPEG a RAW gets, and the original stays untouched underneath.
Where This Stops Working
Three honest edges, because a format list that pretends to have none is a format list you will find the edges of at the worst moment.
A RAW with no usable embedded preview cannot be displayed. It is rare and it is deterministic - the same file fails the same way every time rather than failing intermittently - and the file itself is still stored and still downloadable. But the grid will not have a picture for it.
Time capsules do not take RAW or TIFF. A capsule is sealed and opened years later in a plain browser, so it accepts only the formats a browser paints on its own: JPEG, PNG, HEIC, HEIF, WebP and AVIF. Sealing a .RAF into something that cannot be fixed afterwards is a trap, so the format is refused at the door instead.
Profile pictures cap at 4 MB. Same format list, much smaller ceiling, which in practice is what keeps a 50 MB RAW out of an avatar.
Frequently Asked Questions
What is the best way to share RAW photos with someone?
Upload the RAW files unconverted to a service that shows viewers a generated JPEG and keeps the original for download. Viallo accepts DNG, CR2, CR3, NEF, ARW, ORF, RW2 and RAF, stores each file exactly as uploaded, and opens in a browser with no account on the viewer's side. Dropbox will also hold the files, but its previews are inconsistent across RAW formats, so the recipient may be looking at a filename rather than a photo.
How do I send RAW files without converting them to JPEG?
Skip the export step and upload the files straight off the card. Viallo validates the format by MIME type, extension and the bytes at the head of the file, then stores what arrived rather than a re-encode, so the download later is the same file. Converting first is irreversible, and the highlight and white-balance latitude you shot RAW for is what you lose.
Is it private to upload RAW files to a photo sharing service?
It depends entirely on the service, and the question worth asking is what it does with the contents. Viallo does not run AI scanning over uploaded photos and does not train anything on them, and an album reaches other people through the links you create for it. Google Photos and iCloud both handle RAW well, and both are large platforms whose data practices are worth reading for yourself rather than taking from a comparison table.
What is the difference between a RAW file and the JPEG beside it?
The JPEG is a finished picture and the RAW is the material a picture gets made from. The practical difference is latitude: recoverable highlights, real white-balance changes, and no compression already baked in. Your camera actually writes finished JPEGs inside the RAW too, at more than one size, which is how a good viewer can show you the photograph without processing anything.
My photos are 50 MB each and there are four hundred of them. Is that going to work?
Yes, with the caveat that it is 20 GB and your storage plan has to hold it. Single files are capped at 500 MB, far above anything a camera writes, and they upload in parts rather than as one request, so a frame being enormous is not the problem. Twenty gigabytes is over the free tier's 10 GB, and comfortable inside the 200 GB that comes with Plus.