Convert RAF to PNG

Converting RAF to PNG gives a print-on-demand service a lossless file to work from, carrying the film simulation your Fujifilm camera applied at capture. Because the manufacturer will resize and re-render whatever you send, starting them from a lossless copy is the one part of the chain you control.

  • Where it runs In your browser. The file is never uploaded.
  • Lossy Some detail is traded for size. PNG cannot hold everything an RAF can.
  • File size limit Up to 100 MB per file, free, without an account.
  • Worth knowing This extracts the preview your camera wrote when it took the photograph, at full resolution on almost every camera. It is the camera’s own rendering, so its picture style is baked in and the extra highlight and shadow latitude that is the reason to shoot raw is not in it. Perfect for viewing, sending or uploading; not a substitute for developing the file.

Up to 100 files at once. Mixed formats are fine.

The generations you cannot see happen after the upload

When a photograph becomes a product, it passes through more software than the person who took it usually realises. The platform makes a preview, the layout engine places it into a template, a proof is generated for you to approve, and the production file is rendered for the press. If your upload was a JPEG, several of those steps are re-encodes, and each one starts from the artefacts the previous one introduced.

None of that is visible on a screen and some of it is visible on paper, particularly in smooth gradients and around high-contrast edges — a horizon, a bright window, lettering on a sign. Uploading a lossless file does not stop the platform re-encoding; it stops the chain being longer than it needs to be, and it is the only part of the process the photographer has any say in.

What comes out of the RAF is the camera’s own rendering

The converter finds the largest JPEG Fujifilm embedded in the raw file and writes it into a PNG. That preview is frequently smaller than the full frame, because the camera wrote it for its own screen rather than as a deliverable, so convert one and read the dimensions before assuming you have every pixel the sensor recorded. That picture carries the film simulation, the white balance, the tone curve, the grain effect and the noise reduction the camera applied. It is not a development of the sensor data.

For this particular use that is unusually defensible. A photographer choosing Fujifilm for Classic Chrome or Acros is choosing a rendering, and the camera’s version of that rendering is the reference one. What you cannot do is change it afterwards: the simulation is baked in, an Acros frame stays monochrome, and the highlight and shadow latitude that makes raw worth shooting is not in the extracted picture at all.

Sizing the PNG to the product rather than to the sensor

A print-on-demand product has a physical size and a printing resolution, and between them they decide how many pixels are useful. A 6 by 4 inch postcard at 300 ppi needs 1,800 by 1,200. An A4 print needs about 3,500 by 2,480. A 12 by 12 inch calendar page needs 3,600 square. An X-T5 frame is 7,728 pixels across, which is more than any of those and considerably more than most.

Set a maximum width during the conversion to the number the product needs, with a little margin for the manufacturer’s bleed. It reduces the file by the square of the reduction — cutting 7,728 to 3,600 removes about four fifths of the pixels — which is what turns an upload that fails a size cap into one that succeeds, at no visible cost on the finished object.

The size of a Fujifilm PNG, and why it is not predictable

PNG compresses by finding repetition, and a photograph has almost none. A 26-megapixel preview is 78 MB of raw pixels and typically comes out between 35 and 60 MB; a 40-megapixel one is 119 MB raw and lands roughly between 55 and 90. Read those as the full-resolution case, since the preview is often smaller than the frame. The range within it is wide because it depends on the picture: a studio shot on a plain background compresses well, a woodland scene barely compresses at all.

The encoder here runs an oxipng optimisation pass after the initial encode, which costs about half a second per file and removes roughly two thirds of the bytes the encoder alone would produce. That is a substantial saving on a file of this size and it is applied automatically — there is no setting to enable, and the pixels are identical either way.

Lossless in a PNG means the pixels, not the photograph

Every pixel value stored is recovered exactly, and a PNG resaved a hundred times is bit-for-bit the file it started as. That is the property being bought here and it is a real one. Each chunk also carries a CRC, so a file corrupted in transfer fails loudly rather than displaying with a band of garbage down one side — useful when a large upload goes over a hotel connection.

What it does not mean is that nothing was lost. The picture inside the RAF was compressed by the camera when it wrote the preview, so the PNG is a perfect copy of something that had already been through one lossy stage. Lossless describes the container’s relationship to its contents, not the contents’ relationship to the sensor.

Eight bits, and the sixteen the PNG could have held

PNG supports 16 bits per channel, which sounds like a good home for a 14-bit Fujifilm capture. It is not, because the 14-bit data never reaches the encoder: the embedded preview is an eight-bit JPEG, so the PNG written from it is eight bits with no more tonal range than a web image.

For a print product that is generally sufficient, and it stops being sufficient if the picture will be graded before it goes to press. A 16-bit file that genuinely carries the sensor’s range has to come from a raw developer working on the RAF — Lightroom, Capture One, darktable or Fujifilm’s own software will export exactly that, and it is a different job from the one this page does.

Transparency the PNG offers and a Fujifilm frame does not have

The alpha channel is PNG’s best-known feature and it is empty here. Every pixel recorded by a sensor is fully opaque, so there is nothing transparent in the file for the PNG to carry, and the channel exists in the container without holding anything.

If the product needs a cut-out — an object floating on white, a subject over a coloured background in the template — that is a masking job in an image editor after this conversion, and the PNG is the right format to save the result in. The conversion gives you a container that can hold transparency; it does not create any.

Colour, and the profile the PNG does not carry

No ICC profile is written, so anything opening the file will assume sRGB. Fujifilm bodies have a colour space menu offering sRGB and Adobe RGB, and if the camera is set to Adobe RGB the preview holds Adobe RGB numbers that will be read as sRGB ones — which shows up as saturated colours coming back tamer than intended.

On a make chosen for its colour rendering that is a particularly frustrating way to lose the look, and it is easy to miss until a proof arrives. Print-on-demand platforms almost universally expect sRGB anyway, so setting the camera to sRGB for work destined for print products is the simplest fix, and checking the menu costs nothing.

What the PNG will not tell the manufacturer

The conversion decodes and re-encodes, so no metadata reaches the output: no camera or lens, no exposure settings, no capture date, no copyright field and no GPS coordinate. PNG can hold EXIF and a copyright text chunk; this conversion writes neither.

The copyright one is worth planning around if you are selling the work. Attribution has to travel in the platform’s own listing fields, in the file name, or in a visible credit, because nothing inside the file claims authorship. The absence of a location tag is the compensating gain: a photograph taken in your own garden no longer ships its coordinates with the product listing.

Converting an unreleased Fujifilm set without publishing it first

The RAF is read from disk by the page, scanned for its embedded picture, decoded and written back out as a PNG — all in the tab, with no request carrying the image. The network tab shows it and a disconnected machine proves it.

That matters when the pictures are a product that has not gone on sale. Preparing a print run through a free converter that uploads means the images exist on somebody else’s server before they exist in your shop, under terms you did not read. Here they do not leave the laptop, and a batch of forty frames is limited by your own processor rather than by a queue.

How to prepare a PNG upload from a Fujifilm RAF file

  1. Work out how many pixels the product actually needs and set that as the maximum width.
  2. Drop your RAF files onto this page. The extraction and the PNG encoding both run locally.
  3. Download the PNG files, or take the set as one ZIP, and check the platform’s upload limit before you start.

RAF vs PNG: a camera rendering stored without further loss

RAF compared with PNG
RAFPNG
Full nameFujifilm RawPortable Network Graphics
File extension.raf.png
Media typeimage/x-fuji-rafimage/png
CompressionLossless — nothing is discardedLossless — nothing is discarded
First published20001996
Published byFujifilmPNG Development Group
SpecificationISO/IEC 15948
LicensingProprietaryOpen standard
Standing todayCurrentCurrent
Bit depth1416
Colour it can describeRGBRGB, greyscale, indexed palette
Largest image2,147,483,647 px per side
Opens in a browserNo browserEvery browser
Considered insteadDNG, TIFF, JPGWebP, SVG, JXL

What is lost

PNG has nowhere to put the GPS coordinates, so that goes no further than the RAF. Worth checking before the original is deleted, and worth knowing if the point was to strip it.

What the target format adds

PNG supports transparency and RAF does not. That is room the result has and the original never used — converting does not create a transparent background, it only makes one possible afterwards.

Opening the result

PNG opens in every current browser. RAF has narrower browser support than that. If the file is going onto a web page or into a form, that is usually the whole reason for the conversion.

RAF is a vendor format; PNG is a published specification (ISO/IEC 15948). That matters for anything meant to still open in ten years, when the program that wrote the original may not be around.

The usual programs do not overlap: RAF opens in Adobe Lightroom, Capture One and darktable, PNG in Adobe Photoshop, GIMP and Paint.NET — so whoever receives the result needs something from the second list.

What each format is for

The two are aimed at different work: RAF at photography and editing, PNG at screenshots, line art and logos and the web. That is worth weighing before converting, because the reason one exists is usually the reason the other is awkward.

RAF is Fujifilm's format, published in 2000. It comes out of Fujifilm X-series and GFX bodies. It records 14 bits per channel.

PNG comes from PNG Development Group and dates from 1996, specified as ISO/IEC 15948. Adobe Photoshop, GIMP and Paint.NET all read it.

RAF to PNG: print on demand, file sizes and film simulations

Are my RAF files uploaded anywhere?

No. This conversion runs entirely inside your browser, so the file never leaves your device. You can confirm it yourself: open the network tab of your browser's developer tools and convert something. You will see the page load, plus the analytics and advertising the site is paid for with — and nothing carrying your file. The engine behind this particular pair is a raw preview extractor, which pulls the JPEG the camera already embedded rather than developing the sensor data; your browser fetches it once and caches it.

Why upload a PNG rather than a JPEG?

Because of what happens after the upload. A print-on-demand service typically re-renders your file — resizing it, laying it out, sometimes re-encoding it for a proof and again for production. Each of those steps on a JPEG is another generation of loss on top of the one already in the file. A PNG is lossless, so whatever the service does to it starts from a clean copy rather than a degraded one.

Does the PNG keep the film simulation?

Yes, because the simulation is already in the pixels. The picture extracted from the RAF is the JPEG the camera rendered at capture, with Velvia, Classic Chrome, Acros or whatever was set already applied. PNG stores those pixels exactly, so the look survives the conversion and every subsequent lossless copy of it.

How large will the PNG be?

Larger than you expect and smaller than a TIFF, and it follows the embedded preview rather than the sensor. A preview at the full 6,240 by 4,160 of a 26-megapixel frame is around 78 MB of raw pixel data and typically compresses to between 35 and 60 MB; a full 7,728 by 5,152 lands roughly between 55 and 90 MB. A half-size preview quarters both figures. A dark, simple scene sits at the bottom of the range and a sunlit landscape full of foliage near the top, because PNG compresses repetition and photographs contain very little.

Is this better than shooting JPEG on the camera?

It is the same picture. The camera’s JPEG and the preview inside the RAF are the same rendering, so nothing is gained by the raw file itself on this route. What shooting raw buys you is the option to go back and develop the frame properly if the colour or the exposure turns out to be wrong once you see it printed — which is a real option and worth the card space.

Will the service accept a PNG that size?

Check before converting a set. Many print-on-demand platforms cap uploads at 20, 50 or 100 MB, and some accept only JPEG. If the cap is the problem, set a maximum width during conversion to the largest size the product actually needs — a postcard printed at 300 ppi needs about 1,800 pixels across, not 7,728.

Are my photographs uploaded here to convert them?

No. The RAF is scanned for its embedded picture and the PNG is written, both in your browser, so unreleased work does not travel anywhere before you decide to publish it.

More about these formats

Where these figures come from

The claims this page makes about RAF and PNG are checkable, and these are the documents that settle them.