ToolFeather

PNG to RAW Converter

Turn a PNG into uncompressed raw pixel bytes (RGBA or RGB) and download a .raw file — all in your browser.

PNG to RAW Converter

Drop a PNG here or click to choose

🔒 Decoded in your browser — nothing is uploaded. Output is uncompressed raw pixel bytes (not a camera RAW/DNG file).

🔒 Nothing you enter is sent anywhere or stored. All processing happens in your browser.

How it works

A RAW image file here means the uncompressed pixel data of your image — every pixel written out as bytes, with no PNG/JPEG compression or headers. It's what game engines, graphics tools, and low-level image pipelines sometimes need to load textures or process pixels directly.

Drop in your image and the tool draws it to a canvas, reads the pixels, and lets you download them as a .raw file in either RGBA (four bytes per pixel, including transparency) or RGB (three bytes per pixel). The byte length is exactly width × height × channels, so a 100×100 RGBA image is 40,000 bytes.

Everything runs in your browser — the image is never uploaded. Note this produces raw pixel data; it is not the same as a camera RAW/DNG format, which stores unprocessed sensor data.

Examples

A 512×512 PNG texture → RGBA .raw for a game engine.
Need no transparency? Choose RGB for 3-byte pixels.
A 64×64 icon → a predictable 16,384-byte RGBA buffer.

Raw pixel formats & file size

A raw pixel file stores every pixel as bytes in order, top-left to bottom-right, with no header or compression. The size is fully predictable from the dimensions and the format:

FormatBytes per pixelChannelsSize for 100×100
RGBA4Red, Green, Blue, Alpha40,000 bytes
RGB3Red, Green, Blue30,000 bytes
Grayscale1Luminance only10,000 bytes

Size = width × height × bytes-per-pixel. This tool outputs RGBA or RGB, 8 bits per channel, in row-major order — the layout most engines and image libraries expect when you tell them the width, height and format.

Raw pixel data vs camera RAW

These are different things. Camera RAW (CR2, NEF, ARW, DNG) stores unprocessed sensor data plus metadata and needs special software to open. Raw pixel data (what this tool makes) is just the finished pixels as bytes — there's no header, so whatever reads it must be told the width, height and channel order.

Frequently asked questions

What is a RAW image file in this context?
It's the uncompressed pixel data of your image — each pixel as bytes, with no compression or file header. This is 'raw pixel data', not a camera RAW (CR2/NEF/DNG) sensor file, which is a different thing.
What's the difference between RGBA and RGB output?
RGBA writes four bytes per pixel (red, green, blue, alpha/transparency); RGB writes three (no alpha). RGBA is larger but preserves transparency. Choose RGB if your target doesn't use an alpha channel.
How big will the RAW file be?
Exactly width × height × channels bytes. A 256×256 RGBA image is 262,144 bytes; the same image as RGB is 196,608 bytes. There's no compression, so raw files are larger than the original.
Is my image uploaded?
No. It's decoded and read entirely in your browser, so it never leaves your device.
How do I open or read a .raw file back?
Because a raw file has no header, the program reading it must be told the width, height and pixel format (e.g. 256×256 RGBA). Image editors like Photoshop and GIMP can import raw data if you supply those parameters.
Is this a camera RAW (CR2/NEF/DNG) file?
No. This produces raw pixel bytes, not a camera sensor RAW. See the comparison above — they're unrelated formats despite the shared name.
What byte order and channel order does it use?
8 bits per channel, in RGBA (or RGB) order, stored row by row from the top-left pixel. There's no premultiplied alpha and no padding between rows.