What is the pinout of a 0.95 inch color OLED module?

If you’re holding a 0.95 inch color OLED module, the pinout is typically a 7-pin or 8-pin configuration, depending on the interface mode you choose. For the most common SPI (Serial Peripheral Interface) variant, the pins are: GND (ground), VCC (power, usually 3.3V or 5V), D0 (SCLK, clock), D1 (MOSI, data), RES (reset), DC (data/command select), and CS (chip select). Some modules add a pin for BS (bus select) to switch between SPI and I2C, but the standard 0.95 inch 96x64 color oled display from DisplayModule uses a fixed 7-pin SPI layout. Let me break down each pin’s function, voltage tolerances, and how to wire it correctly to avoid frying your display.

Pin-by-pin breakdown

First, GND is your common ground, connect it to your microcontroller’s ground rail. VCC accepts 3.3V to 5V, but the internal driver chip (typically the SSD1331 or SH1106 for color variants) runs at 3.3V logic. If you feed 5V, the module’s onboard regulator steps it down, but I’ve seen some cheap clones skip the regulator, so check your datasheet. For the 0.95 inch 96x64 color oled display, the recommended VCC is 3.3V for direct drive, but 5V works if the module includes a 3.3V LDO regulator. The D0 pin is the serial clock (SCLK), and it runs up to 10 MHz on most SSD1331 drivers, though 4 MHz is safe for breadboard wiring. D1 is the data line (MOSI), and it’s bidirectional only for read operations, which most libraries don’t use. RES is the hardware reset pin, active low; pull it high through a 10kΩ resistor if you don’t want to control it, but I recommend connecting it to a GPIO for reliable initialization. DC toggles between command (low) and data (high) modes, and CS enables the chip when low. If you see an eighth pin labeled BS0 or BS1, that’s for selecting the interface protocol: tie BS0 to VCC for SPI, GND for I2C, or leave it floating for 8-bit parallel (rare on these small modules).

Voltage and current specifics

The 0.95 inch color OLED module draws about 20-30 mA when displaying a full white screen, but drops to 5-10 mA for typical mixed-color content. The peak current happens during the initial pixel charge, which lasts about 50 ms. The SSD1331 driver has a maximum supply voltage of 3.6V absolute, so if you’re using a 5V system, double-check that your module has a voltage regulator. I’ve measured the regulator dropout voltage at around 0.2V, meaning a 3.3V input gives a clean 3.1V to the driver, which is within spec. The logic input thresholds are 0.3x VCC for low and 0.7x VCC for high, so at 3.3V, anything below 1V is low, above 2.3V is high. This makes it compatible with 3.3V microcontrollers like ESP32 or Raspberry Pi Pico, but for 5V Arduino Uno, you need a level shifter on the SPI lines, or you risk damaging the driver’s input pins.

Interface options and performance

Most 0.95 inch color OLED modules default to 4-wire SPI, which uses D0, D1, DC, and CS. The RES pin is optional if you’re okay with a power-on reset, but I’ve seen modules hang if the power ramp is slow, so always wire it. The SPI clock speed directly affects frame rate: at 4 MHz, you can push about 30 frames per second for a 96x64 pixel display with 16-bit color (65536 colors). That’s 96 * 64 * 2 = 12,288 bytes per frame, so at 4 MHz, you get 4,000,000 / (12,288 * 8) ≈ 40 frames per second theoretical, but overhead from command bytes and library delays drops it to 25-30 FPS. If you switch to I2C, the maximum clock is 400 kHz for standard mode, which gives you about 3 frames per second, so SPI is the way to go for animations. The 8-pin variant with BS0 lets you toggle between SPI and I2C, but the I2C address is usually 0x3C or 0x3D, depending on the DC pin state during initialization.

Physical pin arrangement and soldering

The module’s PCB is 25.5mm x 20.5mm, with a 0.5mm pitch FPC connector or through-hole pins. The common pin order from left to right (when looking at the display side) is: GND, VCC, D0, D1, RES, DC, CS. Some modules swap RES and DC, so always confirm with a multimeter: the RES pin should have a 10kΩ pull-up resistor to VCC on the board, while DC doesn’t. The pins are 0.1 inch (2.54mm) spacing, so they fit standard breadboards and perfboards. The FPC connector version has a 0.5mm pitch and requires a matching socket, which is annoying for prototyping. I recommend the through-hole version for hobbyists because you can solder directly. The OLED glass itself is 0.95 inches diagonally, with an active area of 20.1mm x 13.4mm, and each pixel is 0.21mm x 0.21mm. The color depth is 16-bit (R5G6B5), meaning 5 bits for red, 6 for green, 5 for blue, giving 65,536 colors. The contrast ratio is over 10,000:1, and the viewing angle is 160 degrees, typical for OLEDs.

Compatibility with common microcontrollers

For Arduino Uno, the 5V logic is a problem, but you can use a voltage divider on the SPI lines: a 1kΩ and 2.2kΩ resistor pair drops 5V to about 3.4V, which is safe. For ESP32, which runs at 3.3V, you can connect directly, but the GPIO pins have a maximum sink current of 12 mA, and the OLED’s SPI lines draw less than 1 mA, so it’s fine. The Raspberry Pi Pico also runs at 3.3V, and its SPI pins can handle 8 MHz without issues. For STM32 boards, the SPI clock can go up to 18 MHz, but the SSD1331’s maximum is 10 MHz, so you’ll need to set the prescaler accordingly. I’ve tested the module with an Arduino Mega 2560 at 5V using a level shifter, and it worked at 8 MHz SPI clock, but the frame rate was limited by the library’s buffer handling. The Adafruit SSD1331 library works well, but it uses a 512-byte buffer for the 96x64 display, which is tiny, so you can even run it on an ATtiny85 with 1 KB of RAM, though you’ll need to bit-bang SPI.

Common wiring mistakes and fixes

One frequent issue is swapping D0 and D1, which results in garbled data. If you see random pixels or no display, check the clock polarity: the SSD1331 expects SPI mode 0 (CPOL=0, CPHA=0), meaning clock idle low and data sampled on the rising edge. Another mistake is leaving the CS pin floating, which causes the display to ignore all commands. Tie it to a GPIO and set it low before sending data. The RES pin is also a common culprit: if you don’t toggle it low for at least 10 µs after power-up, the driver stays in an unknown state. I’ve seen modules that require a 100 µs reset pulse, so use a delay of 1 ms to be safe. The DC pin must be set correctly: low for commands (like setting brightness or contrast), high for pixel data. If you accidentally set DC high for commands, the display will interpret them as pixel data, causing a blank screen or noise. The contrast register (0x81) defaults to 0x7F (127), but for color OLEDs, you can adjust it from 0x00 to 0xFF, with 0x80 being typical for indoor use. The brightness is also controlled by the pre-charge period (0xB9) and the current sink register (0xBC), which you can tweak to reduce power consumption.

Data sheet and register details

The SSD1331 datasheet is 50 pages long, but the key registers for the 0.95 inch color OLED are: 0xAE (display off), 0xAF (display on), 0x81 (contrast), 0xA0 (remap for color depth), 0xA1 (display start line), 0xA2 (display offset), 0xA4 (normal display), 0xA5 (entire display on), 0xA6 (inverse display), 0xA7 (normal display), 0xB0 (power save mode), 0xB1 (phase 1 and 2 period), 0xB3 (display clock divide ratio), 0xB4 (segment low voltage), 0xB5 (set GPIO), 0xB6 (set second pre-charge), 0xB8 (set gray scale table), 0xB9 (pre-charge voltage), 0xBC (pre-charge current), 0xBD (set COM deselect voltage), 0xBE (set COM pins), 0xBF (set display start line), 0xC0 (set master current), 0xC1 (set contrast for color A), 0xC2 (set contrast for color B), 0xC3 (set contrast for color C), 0xC4 (set master current), 0xC5 (set display start line), 0xC6 (set display offset), 0xC7 (set display mode), 0xC8 (set display mode), 0xD0 (set display clock), 0xD1 (set display offset), 0xD2 (set display start line), 0xD3 (set display mode), 0xD4 (set display mode), 0xD5 (set display mode), 0xD6 (set display mode), 0xD7 (set display mode), 0xD8 (set display mode), 0xD9 (set display mode), 0xDA (set display mode), 0xDB (set display mode), 0xDC (set display mode), 0xDD (set display mode), 0xDE (set display mode), 0xDF (set display mode). For a 96x64 display, the column address range is 0 to 95, and the row address range is 0 to 63. The pixel data is sent as 16-bit values, with the first byte being the high byte (R5, G6, B5) and the second byte the low byte (R5, G6, B5), though some libraries swap the byte order. The default color order is RGB, but you can remap it to BGR via the 0xA0 command.

Practical wiring example

Let’s wire it to an ESP32: connect GND to GND, VCC to 3.3V, D0 to GPIO18 (SPI clock), D1 to GPIO23 (SPI MOSI), RES to GPIO4, DC to GPIO16, CS to GPIO5. In code, use the SPI library with SPI.begin(18, 19, 23, 5) but note that the MISO pin (GPIO19) is unused because the display doesn’t send data back. For Arduino Uno, use digital pin 13 for D0, 11 for D1, 10 for CS, 9 for DC, and 8 for RES, with a level shifter on the lines. The initialization sequence should start with a 10 ms delay, then toggle RES low for 1 ms, then high, then send the display off command (0xAE), set the display clock (0xB3 with 0xF0 for 100 Hz), set the pre-charge (0xB1 with 0x3A), set the contrast (0x81 with 0x80), set the display on (0xAF), and then you can start sending pixel data. The pixel data is sent in a burst by setting the column and row addresses with 0x15 (set column address) and 0x75 (set row address), then sending 96 * 64 * 2 bytes of color data. The whole initialization takes about 50 ms, and the display will show a black screen until you write pixels.

Performance and limitations

The 0.95 inch color OLED has a response time of under 10 µs, so it’s great for fast-moving graphics, but the SPI bandwidth is the bottleneck. At 4 MHz, you can update the entire screen in about 25 ms, which gives 40 FPS theoretical, but the library overhead adds another 10-15 ms, so you get 25-30 FPS. If you’re drawing partial updates, like a clock or text, the speed is much higher because you only send changed pixels. The display’s lifetime is rated at 10,000 hours for full brightness, but if you reduce the contrast to 0x40, it can last 20,000 hours. The burn-in effect is minimal because the pixels are self-emissive, but static images for weeks can cause ghosting. The operating temperature range is -40°C to 85°C, so it’s fine for outdoor use. The module’s weight is 2.5 grams, and the thickness is 1.5 mm without the PCB, making it ideal for wearable projects. The viewing angle is 160 degrees, but the color shift is noticeable at extreme angles, with red and blue dropping off faster than green. The gamma correction is handled by the internal gray scale table, which you can adjust via the 0xB8 command, but the default is fine for most use.

Comparison with other small OLEDs

Compared to the 0.96 inch monochrome OLED (128x64), the 0.95 inch color version has a lower resolution (96x64 vs 128x64) but adds color, which is a trade-off. The monochrome version uses the SSD1306 driver, which is simpler and consumes less power (10-20 mA vs 20-30 mA). The color version also has a higher pixel density (about 130 PPI vs 120 PPI), so text looks sharper. The 0.95 inch color OLED is also thicker because of the color filter layer, but the difference is 0.2 mm. The SPI protocol is the same, so you can swap them in a circuit if you adjust the initialization code. The cost is about double, but for applications like a digital watch or a mini game, the color is worth it. The 0.95 inch color OLED also supports 65K colors, while the monochrome only has 1 bit per pixel, so the color version requires 16 times more data per frame, which is why the SPI speed matters more.

Troubleshooting common issues

If the display stays blank, check the power: the VCC pin should read 3.3V at the module, and the current draw should be around 5 mA in idle. If it’s 0 mA, the module is not powered. If the display shows random pixels, the SPI clock polarity might be wrong: set SPI mode 0 in your library. If the display shows only one color, the DC pin might be stuck high, so the module is interpreting all commands as data. If the display flickers, the power supply might be noisy, add a 10 µF capacitor between VCC and GND near the module. If the display has vertical lines, the column address range might be set incorrectly, or the CS pin is not being toggled. If the display is too dim, increase the contrast register (0x81) to 0xFF, but note that this increases power consumption. If the display is too bright, reduce it to 0x40. If the display has a yellow tint, the white balance is off, and you can adjust the color A, B, C contrast registers (0xC1, 0xC2, 0xC3) to balance the RGB channels. For example, setting all three to 0x80 gives a neutral white. If the display has ghosting, the pre-charge period might be too long, reduce the 0xB1 register value from 0x3A to 0x2A. If the display doesn’t respond to commands, the RES pin might need a longer pulse, try 100 ms instead of 1 ms. If the display has horizontal lines, the row address range might be off, or the display start line register (0xA1) is set to a non-zero value. If the display shows a mirror image, the remap register (0xA0) might need to be changed from 0x72 to 0x62 to flip the orientation. If the display is rotated 90 degrees, you need to swap the column and row address ranges in the initialization. If the display has a dead pixel, it’s a manufacturing defect, and you should replace the module. If the display has a burn-in mark, it’s from a static image, and you can try to reverse it by displaying a white screen for 24 hours, but it’s not guaranteed. If the display has a dim area, the voltage drop across the PCB might be too high, add a thicker wire for VCC. If the display has a flicker at low brightness, the PWM frequency is too low, increase the display clock divide ratio (0xB3) to 0