What Is Bit Depth in Images? 8-Bit vs. 16-Bit and When It Matters

Bit depth is the number of tonal values available for each color channel in an image. Use RAW capture and a 16-bit-per-channel working file when you expect substantial exposure, white-balance, color, or gradient edits. Use an 8-bit export when the destination requires it or sharing compatibility is the priority.

A 16-bit file does not automatically look better on screen. Its main benefit is preserving more precision while you edit.

Bit depth describes tonal precision, not resolution

In a raster image, bit depth measures how much color information is available per pixel. For RGB images, the useful label is usually bits per channel: the precision assigned separately to red, green, and blue.

The number of available values per channel follows:

An 8-bit RGB image therefore has 256 possible values for red, green, and blue individually, producing more than 16 million possible RGB combinations.

Two labels often cause confusion:

1
1. 8-bit per channel RGB uses 8 bits for each of three channels.
2
2. 24-bit RGB means the same thing expressed as total RGB storage: 8 bits × 3 channels = 24 bits per pixel.

By contrast, 16 bits per channel means 16 bits for each RGB channel-not 16 bits for the whole pixel.

Bit depth is also separate from:

1
1. Resolution: the number of pixels in the image.
2
2. Color gamut: the range of colors a color space can describe.
3
3. Compression: how image data is stored or reduced.
4
4. Display and print capability: the values a file can encode are not proof that every display or printer can reproduce them.

Keep capture, editing, and export depth separate

"16-bit image" can refer to different stages of a workflow. Treat these as separate decisions.

1. Capture: RAW preserves unprocessed camera data

A camera RAW file contains unprocessed data from the camera and must be converted into a viewable image. RAW is not one universal format; different camera makers use different RAW formats.

A camera's RAW bit depth is also not necessarily 16 bits per channel. For example, one camera can record RAW at 12 or 14 bits, while an editing application may offer a 16-bit-per-channel RGB working mode.

A 16-bit RGB working document provides more numerical room for subsequent processing.

2. Editing: use 16-bit per channel when you will push the image

A 16-bit working document is most useful when the image needs large changes, such as:

1
1. Raising exposure substantially in a dark photograph
2
2. Making large white-balance or color adjustments
3
3. Adjusting a smooth sky, studio backdrop, or other gradual gradient
4
4. Applying several tonal or color corrections before final rendering

Large edits made from RAW data can produce fewer visible artifacts than equivalent edits applied to an already rendered image. RAW conversion can also perform adjustments before the image is committed to a viewable RGB result.

The practical question is not "Is 16-bit always better?" but "Will this image undergo edits that make small tonal gaps visible?"

3. Delivery: export the file the destination can use

Keep the RAW file or higher-precision master when it matters to your work. Then create a separate delivery copy for the website, client, print workflow, app, or sharing service.

This approach avoids making a permanent quality tradeoff just because one destination needs an 8-bit file.

Why banding appears in skies and gradients

Banding, also called posterization, is the appearance of visible stripes or steps where a smooth transition should be-such as in a blue sky, a sunset, a shadow gradient, or a softly lit background.

Bit depth can matter because an image with fewer available encoded values has fewer tonal steps to work with. But it is not the only cause of posterization. Rendering and processing order matter too: posterization can result when calculations are performed on already rendered data rather than from the RAW base data.

A practical way to think about it:

1
1. Smooth source + heavy edits: Retaining RAW data and using a higher-precision working document gives editing operations more room before the result is rendered.
2
2. Visible stripes after editing: Go back to the RAW file or higher-precision master rather than repeatedly editing the reduced export.

Higher bit depth generally increases file size, so it is not automatically the best choice for every copy of every image. Use it where editing flexibility is valuable, then make a smaller or more compatible derivative when needed.

Some editing features may only work on an 8-bit copy. In that case, keep the 16-bit original and create a separate 8-bit version for that feature instead of converting the master permanently.

Working rule: convert to 8-bit late in the workflow-after major tonal, color, and gradient-sensitive edits are complete.

PNG: lossless, with support for higher sample depth

PNG is a lossless raster-image format. It supports sample depths from 1 to 16 bits, although the allowed depths depend on the PNG color type. All channels in a PNG image use the same sample depth. See the PNG specification's bit-depth rules.

Use PNG when you need a lossless raster export and your export path supports the sample depth you intend to preserve.

One important exception: in an indexed-color PNG, bit depth refers to bits per palette index, not directly to per-channel color precision. Do not assume every PNG labeled with a particular bit depth is equivalent to an RGB or grayscale image at that depth.

Lossless PNG encoding also cannot restore information that was already reduced during conversion or earlier rendering.

Choose JPEG or HEIF by delivery requirements

Do not rank file types solely by their extension or a single bit-depth number.

One camera specification, for example, distinguishes 14-bit RAW, 8-bit JPEG, and 10-bit HEIF capture. That is an example of one device's recording options-not a universal rule for all JPEG or HEIF files.

HEIF needs particular caution because it is a container format. The container name alone does not specify one codec or one quality setting, and support can vary among devices, applications, and services. Sharing workflows may also have limited HEIF compatibility or convert HEIF files to JPEG.

For a final export:

1
1. Keep the higher-precision master if you may revisit the edit.
2
2. Confirm the destination's requirements for file type and compatibility.
3
3. Export an 8-bit derivative when that is what the destination expects.
4
4. Use PNG when a lossless raster export and supported sample depth are needed.
5
5. Test HEIF sharing paths when compatibility matters, rather than assuming every recipient or service will handle it the same way.