DS3231 RTC Chips, Clock Modules and Timing Boards

DS3231 real-time clocks: chips, breakout boards and finished clocks

Find parts for retaining calendar time in data loggers, microcontroller projects and timed equipment. This collection includes bare DS3231SN and DS3231M-family RTC ICs, standard and mini I²C breakout boards, battery-backed modules with or without AT24C32 EEPROM, Raspberry Pi Pico-oriented boards, and some complete LED or nixie clock projects. It also includes multi-model listings in which the purchased option may instead be a DS1302, DS1307, PCF8563, PCF8523, SD3078, sensor or unrelated IC. The product title is a search label, not a bill of materials: always use the selected variant to identify the actual item and pack quantity.

What an RTC provides

An RTC keeps seconds, minutes, hours and calendar fields available to a host processor, including during loss of main power when a suitable backup source is fitted. A DS3231-family device communicates over a two-wire I²C bus and can support alarms and timing outputs according to its specific part and board implementation. A bare RTC or breakout does not display the time independently: a microcontroller, suitable software, an initial time-setting step and a display or other application hardware are needed for a visible clock. EEPROM, battery, connectors, headers, cable and enclosure are not inherent to the IC; they must be verified for the exact selected product.

DS3231SN versus DS3231M: do not merge the specifications

• DS3231SN / DS3231S, usually 16-lead SOIC/SOP listings: Bare-chip options described as 16-pin RTCs are component-only purchases; they do not contain a carrier board or removable coin cell. DS3231SN uses an integrated temperature-compensated crystal timebase. A manufacturer's ±2 ppm figure, where applicable, belongs to the specified DS3231 device and temperature interval, not to every assembled board or another model. Check marking, manufacturer documentation, package drawing and the operating conditions of the selected IC.
• DS3231M / DS3231MZ, usually 8-lead SOIC/SOP listings: This is a distinct MEMS-based RTC family. Do not call it a DS3231SN 16-pin chip or apply SN timing accuracy or footprint to it. A listing for a DS3231M module can itself contain conflicting copied text about a 16-pin crystal-based device; confirm the actual mounted chip and board circuit before claiming either architecture or grade.
• Mixed SN/M options: Some products explicitly offer DS3231M SOP-8 and DS3231SN SOP-16 as separate variants. They are not pin-for-pin substitutions, and a selection of one does not deliver both. Titles that say 'DS3231SN/M' without an independently confirmed suffix should not be used as an accuracy guarantee for either family.

Standard RTC boards, mini modules and memory

A populated DS3231 board may provide convenient header pins, a battery holder and, on some versions, an AT24C32 EEPROM. Standard module listings often distinguish 1-, 2-, 3-, 5-, 10-, 30- or 50-board quantities; mini versions can have a different layout and fitted components from the larger board. Blue/yellow PCB choices, mini/standard choices and with-battery/without-battery options must be read separately. A selection marked 'Dupont Cable 15CM' can be the cable alone, whereas a 'DS3231 with cable' selection indicates a bundle; do not treat an accessory-only option as an RTC.

AT24C32 capacity is 32 kilobits, approximately 4 kilobytes, not 32 kilobytes. Several supplier descriptions use '32KB' for this part; that is a units error. The EEPROM is additional nonvolatile storage and is not needed to make the RTC keep time. On boards that include it, its I²C address and address-jumper arrangement must be checked on the actual PCB. Do not assume every mini board, bare chip, finished clock or third-party breakout contains AT24C32 simply because another option does.

Compact breakout products here include listings described as ChronoDot-style, STEMMA QT/Qwiic-compatible and Raspberry Pi Pico-specific. Connector presence, cable inclusion, supplied headers, cell format, logic-level accommodation and board footprint differ. One STEMMA QT-style listing describes a CR1220 backup holder and says the QT cable and cell are not included; do not substitute the CR2032 cell assumptions of larger ZS-042-style modules for that breakout. A board described as compatible with a Raspberry Pi Pico does not automatically include the Pico or guarantee direct physical compatibility with every Raspberry Pi or microcontroller.

Battery backup: the critical safety check

Backup timekeeping requires the correct cell and an intact backup circuit, and listings vary between included batteries, empty holders and no-battery choices. More importantly, some common RTC boards have a charging path intended for a rechargeable cell such as LIR2032. Do not insert a non-rechargeable CR2032 into a circuit that may charge it while main power is present. Supplier listings in this collection sometimes recommend both LIR2032 and CR2032 for the same board, or say to remove a CR2032 whenever power is applied. That is not a verified, safe universal instruction. Inspect the exact board revision, charging components and battery documentation or obtain qualified confirmation before choosing and installing a cell. Never infer a supplied cell type or safe charging behavior solely from the phrase 'with battery'. Follow applicable handling and shipping rules for cells.

I²C and system integration considerations

1. Confirm the selected RTC device: Read the suffix and physical package first. DS3231SN, DS3231M, DS1307, DS1302, PCF8563 and PCF8523 require their own datasheets and can differ in bus interface, pin mapping, timebase and software support. DS1302 is not simply another I²C DS3231 option.
2. Verify supply and logic levels at board level: Some module listings describe 3.3 V and 5 V systems, but onboard pull-ups, EEPROM, indicators and charging circuits affect integration. Confirm the actual board schematic and the host's I/O tolerance; a chip voltage rating alone does not certify a complete module as safely interchangeable between hosts.
3. Plan the I²C bus: Check the RTC address and any separate EEPROM address against other attached devices. Decide whether pull-up resistors already exist on the RTC PCB or host; assess bus capacitance and wiring length for the intended speed. Do not assume that a connector or four-pin header solves electrical compatibility.
4. Set and validate the clock: After assembly, initialize the time from a reliable reference, verify date rollover, time format and alarm behavior in application firmware, and test backup operation across power interruptions. Time zone and daylight-saving rules belong in the host application's software; an RTC generally stores time values rather than worldwide civil-time policy.
5. Validate accuracy under real conditions: Compare the exact suffix's datasheet and measured drift over your temperature range. Do not extend a ±2 ppm claim at one temperature interval to all variants or promise a fixed 'one minute per year' in every installation. Temperature readout from a DS3231 is principally associated with its compensation system, not a calibrated environmental sensor for every project.

Other RTC families and misleading multi-option listings

Several product listings offer PCF8563/PCF8563T modules with titles that say 'better than DS3231'. The selected device in those listings is PCF8563, not DS3231, and no comparative accuracy claim should be accepted without a defined test condition. Other options explicitly choose DS1307, DS1302, PCF8523T, SD3078 or Raspberry Pi RTC accessories. Likewise, multi-chip listings can offer DS3231SN alongside IR2010S, IR2103S, memory ICs, op amps, switching controllers or unrelated parts; the selected non-RTC variant remains that other component. One sensor-module title includes DS3231 in a long list, yet some products' currently selectable options are DHT11, sound, rain, soil or RF sensors rather than a clock. Buying one selected sensor option does not deliver every module mentioned in the title or necessarily any RTC.

Finished clocks, kits and controller boards

A 6-digit USB-powered LED clock listing provides selectable display colors and a separate 'case' option; do not assume the enclosure comes with a color option. Other products are DIY dot-matrix alarm clock kits, IN-12 or IN-14 nixie/glow-tube clock assemblies, and RGB display projects. Their 'with tubes', 'no tubes', 'already soldered' and 'need to solder' selections materially change the supplied hardware. A finished or partially assembled clock is not a bag of DS3231 chips; check display, tube, power adapter, battery, case and assembly requirements for each selected variant. Nixie-based projects can contain hazardous high-voltage circuitry even if their external input is low voltage, so assembly and service require appropriate expertise.

The collection also contains ESP32-based multi-channel relay controllers that describe an onboard DS3231, including A16S-type boards and a larger F24 controller with selectable 12 V or 24 V relay version. These are complete automation boards, not RTC breakout modules. Check their own power, firmware, connectivity and relay-contact requirements; do not generalize a controller's relay or certification claim to the DS3231 chip or to other products here. For mains or other hazardous loads, use qualified electrical design and installation rather than a generic collection-level wiring procedure.

Before ordering: model, format and contents

For a PCB design, select the exact bare-chip suffix and footprint. For prototyping, determine whether you want a populated board and whether AT24C32, headers, a compatible connector and backup holder are present. For a visible time display, select an actual clock or a separate display project, not just an RTC board. For replacement or repair, compare chip marking, oscillator family, package, pinout, host supply and firmware. Finally check the active purchase variant's quantity and included items, particularly battery, cable, case, tube and board assembly. Titles and copied supplier descriptions can disagree: when model identity or battery circuit is uncertain, confirm the delivered hardware before building around it.

Frequently asked questions

Does every DS3231 listing include an AT24C32? No. A bare RTC chip has no separate EEPROM, and breakout boards vary. The AT24C32, when present, provides 32 Kb or approximately 4 KB.

Are DS3231SN and DS3231M the same chip in different packages? No. They are different oscillator families and generally different package footprints; compare the exact device specifications, not just the common DS3231 prefix.

Can I put a CR2032 into any board with a coin-cell holder? No. First verify whether the actual board can charge the installed cell. A non-rechargeable battery must never be charged.

Is an RTC module a ready-to-use display clock? Usually not. Most modules expose time data to a host over I²C; the complete LED and nixie clocks in this collection are separate products with their own purchase options.