# Using RGB texture format for image load/store

As stated in documentation possible values for layout qualifiers of image formats are (for example floating point):

Floating-point layout image formats:

• rgba32f
• rgba16f
• rg32f
• rg16f
• r11f_g11f_b10f
• r32f
• r16f
• rgba16
• rgb10_a2
• rgba8
• rg16
• rg8
• r16
• r8
• rgba16_snorm
• rgba8_snorm
• rg16_snorm
• rg8_snorm
• r16_snorm
• r8_snorm

So we can use R, RG and RGBA formats. But why RGB (except r11f_g11f_b10f) is not allowed?

• R11F_G11F_B10F is an RGB format. – Nicol Bolas Jan 15 '17 at 1:44
• Keep in mind that the docs don't list all possible formats. There are often vendor-specific formats, and formats that came after the docs were written. – user1118321 Jan 15 '17 at 3:04
• @NicolBolas Yeah because it has 32 bits overall, now I see it. – narthex Jan 15 '17 at 10:19

RGB8 format and similar are often not supported by GPUs (or only supported for a subset of GPU operations) because they don't have a power-of-two number of bytes per pixel. RGB8 would be 24 bits or 3 bytes per pixel. All the formats in that list have 1, 2, 4, 8, or 16 bytes per pixel.

Using a power of two simplifies addressing calculations in the hardware, because it can be implemented using a shift instead of a full multiply. (A shift by a fixed value such as 2 bits can even be implemented in hardware without any actual "calculations" at all, just by routing wires.) It also means that pixels are always nicely aligned with respect to boundaries of memory pages, cache lines, etc., which no doubt simplifies many things in the hardware.