Arduino Project Ideas: 30 Projects from Beginner to Advanced

Looking for Arduino project ideas? You're in the right place: this list has 30 projects across beginner, intermediate and advanced levels, and the tables tell you what each one does, what it teaches you and which parts it needs. The ideas get gradually harder, from lighting an LED to an obstacle-avoiding robot, and each level builds on what you learned in the one before. At the end you'll also find six bonus ideas for the Wi-Fi-enabled ESP32 and the MicroPython-programmed Raspberry Pi Pico, plus a practical method for planning a project from start to finish.

The best way to use this list is to pick a project from the table for your level, build the basic version first and then improve it with small additions. Adding a buzzer to the night light or a display to the parking sensor, for example, often teaches you more than starting a brand-new project from scratch. Most of the projects in the tables are in the BlueGrays app with a step-by-step circuit diagram and code; the "In BlueGrays" column shows the matching projects.

Before you start: which parts do you need?

All of the first 7 projects can be built with one basic kit: an Arduino Uno (or Nano), a breadboard, male-to-male jumper wires, a few coloured LEDs plus an RGB LED, 220 Ω and 10 kΩ resistors, push buttons, a potentiometer, an LDR and a passive buzzer. For projects 8–10 you add an HC-SR04 distance sensor, an SG90 servo and a PIR motion sensor; most starter kits already include all three. At the intermediate level, modules such as the DHT11, an I2C LCD, an IR receiver and remote, a 7-segment display and a WS2812B LED strip come in. At the advanced level you need parts like motor drivers, relays and an external power supply. To decide which kit to buy, see the Arduino starter kit guide; for choosing a board, read Which Arduino Should I Buy?, and for the breadboard's internal connections, What Is a Breadboard?.

Beginner level: 10 easy Arduino projects

Projects at this level teach three basic skills: digital output (lighting an LED), digital input (reading a button) and analog input (reading a sensor). Always put a resistor in front of every LED; for a standard red LED running from 5 V, 220 Ω gives about 14 mA, which is safe. You can find the right value for other colours with the LED resistor calculator.

• LED projects (1–3): the LED's long leg (anode) goes to positive and the short leg (cathode) to negative. You'll find details on the legs and choosing a resistor in What Is an LED? and What Is a Resistor?. Adjusting the yellow time and adding a pedestrian button to the traffic light makes a nice first upgrade.
• Button project (4): if you wire the button with INPUT_PULLUP you don't need an external resistor. Debouncing is a must so one press isn't counted several times; the button wiring article covers both methods.
• Night light (5): the LDR and the 10 kΩ resistor form a voltage divider, and analogRead returns a value between 0 and 1023. Set the threshold by measuring in your own room; details are in the LDR light sensor article.
• Melody (6): an active buzzer only produces a single tone; for a melody you need a passive buzzer. You can see the difference in What Is a Buzzer?.
• RGB LED (7): common-anode and common-cathode models use opposite logic; pick the wrong type and the colours come out inverted. The RGB LED guide explains both types.
• Sensor projects (8–10): the HC-SR04, the servo motor and the PIR sensor are the building blocks of the next level; getting each one working on its own first makes intermediate projects much easier.

Intermediate level: 10 Arduino projects

At the intermediate level you no longer use a single part but several modules together: you show a sensor reading on a display, switch an LED with a command from a remote, or speed up a buzzer based on a measurement. Two skills stand out here: installing libraries and timing with millis(). A parking sensor written with delay() can't make a proper sound while it measures; with millis() both happen at the same time.

• Parking sensor (11): dividing the HC-SR04's echo time in microseconds by 58 gives the distance in centimetres. You'll find this project's non-blocking code in the planning section below; sensor details are in the HC-SR04 article.
• Temperature display (12): don't read the DHT11 more than once per second; the sensor produces at most one new value per second. Connecting the display over I2C takes only 4 wires; see DHT11 and I2C LCD display.
• Digital clock and dice (14, 17): with 7-segment displays the difference between common anode and common cathode is critical; the 7-segment display article gives the segment tables.
• Remote and Bluetooth (15, 18): every button on an IR remote has its own code, so you first need to read those codes on the serial monitor. Details are in the IR receiver and remote and HC-05 Bluetooth module articles.
• NeoPixel (20): each WS2812B LED can draw about 60 mA at full white, so a 30-LED strip can reach 1.8 A. Details are in the WS2812B NeoPixel article.

Advanced level: 10 Arduino projects

Advanced projects bring together several sensors, motors and real-world loads. Here power design and mechanics matter as much as code: powering the motors separately, wiring the relay safely, securing the cables firmly. In the code, thinking in state machines makes your life easier: for example, you define a lock's states such as "waiting, entering code, open, alarm" separately and in each state do only the work that belongs to it.

• Lock projects (21–22): saving the code in EEPROM instead of hard-coding it keeps your settings even when the board is switched off and on again. For wiring, see the Keypad and RFID RC522 articles; remember that the RC522 runs on 3.3 V.
• Robots (23–24): DC motors don't connect directly to an Arduino pin; you need a driver such as the L298N. The L298N drops 2 V or more, so power 6 V motors from a 7–9 V supply. Details are in the DC motor control with L298N article.
• Smart irrigation (25): cheap resistive soil sensors corrode if they're powered all the time; power the sensor from a pin only while measuring. Use a relay for the pump; see soil moisture sensor and relay module.
• Gas alarm (26): the MQ-2's heater needs a few minutes to warm up every time it's powered on; set the threshold by measuring in clean air after warm-up. Details are in the MQ-2 gas sensor article.
• Games (28–29): the OLED's 1 KB frame buffer takes up half of the Uno's 2 KB of RAM, so keep an eye on memory use in games. You can use a joystick instead of buttons for control; for the display, see the OLED SSD1306 article.

6 bonus ideas with the ESP32 and Raspberry Pi Pico

If your project needs to connect to the internet, be controlled from a phone or send data to a server, switching from the Arduino Uno to the ESP32 is the easiest route: Wi-Fi and Bluetooth are built in, and it's programmed with the same Arduino IDE. The Raspberry Pi Pico, on the other hand, is cheap and fast and can be programmed in MicroPython, which makes it great if you want to learn Python. You can decide between them with the Arduino or ESP32? comparison, and get started with the What Is the ESP32? and What Is the Raspberry Pi Pico? articles.

How do you plan a project from start to finish?

1. Describe what it does in one sentence: "If an obstacle is closer than 50 cm, the beeping should speed up." If the sentence is clear, so is the project.
2. List the inputs and outputs: inputs are sensors and buttons; outputs are LEDs, buzzers, motors and displays. Give each one a pin; you can see your board's pin map in the Pinout tool.
3. Work out the power budget: add up the current each part draws. An Arduino Uno pin can supply 40 mA as an absolute maximum, and you shouldn't exceed 20 mA for safe operation; for more, use a transistor, relay or driver. The Ohm's law tool handles the calculations.
4. Test each module on its own: read the sensor on the serial monitor first and play the buzzer with a separate sketch. If you wire everything at once and it doesn't work, finding the fault becomes much harder.
5. Combine the parts: merge the code into a single loop() using millis() instead of delay(), so every task runs at its own time.
6. Box it up and document it: photograph the working circuit and keep the wiring table and the code. You'll save a lot of time when you use the same parts in your next project.

Let's apply these steps to the intermediate parking sensor project. The input is the HC-SR04 (TRIG pin 9, ECHO pin 10) and the output is a passive buzzer (pin 8). The sensor draws about 15 mA and a small passive buzzer stays within the pin's limits, so the total current is easily covered by USB. The code below measures the distance about 16 times a second and, when an obstacle is closer than 50 cm, makes the beeps faster in proportion to the distance: each beep and the silence after it last 10 ms per centimetre, so 400 ms at 40 cm and 100 ms at 10 cm. Below 5 cm the tone becomes continuous.

1const int TRIG = 9;
2const int ECHO = 10;
3const int BUZZER = 8;                       // pasif buzzer / passive buzzer
4
5unsigned long olcumZaman = 0, bipZaman = 0;
6long mesafe = 400;                          // cm
7bool bipAcik = false, sesCaliyor = false;
8
9long mesafeOlc() {
10  digitalWrite(TRIG, LOW);
11  delayMicroseconds(2);
12  digitalWrite(TRIG, HIGH);
13  delayMicroseconds(10);                    // 10 µs tetik darbesi / 10 µs trigger pulse
14  digitalWrite(TRIG, LOW);
15  unsigned long sure = pulseIn(ECHO, HIGH, 30000UL);  // en fazla 30 ms bekle / wait at most 30 ms
16  if (sure == 0) return 400;                // yankı yok: engel uzakta / no echo: obstacle is far
17  return sure / 58;                         // µs -> cm
18}
19
20void setup() {
21  pinMode(TRIG, OUTPUT);
22  pinMode(ECHO, INPUT);
23  pinMode(BUZZER, OUTPUT);
24}
25
26void loop() {
27  unsigned long simdi = millis();
28  if (simdi - olcumZaman >= 60) {           // saniyede yaklaşık 16 ölçüm / about 16 readings per second
29    olcumZaman = simdi;
30    mesafe = mesafeOlc();
31  }
32
33  bool sesli = false;
34  if (mesafe < 5) {                         // çok yakın: sürekli ses / very close: continuous tone
35    sesli = true;
36  } else if (mesafe < 50) {                 // yaklaştıkça bipler sıklaşır / beeps speed up as it gets closer
37    if (simdi - bipZaman >= (unsigned long)mesafe * 10) {
38      bipZaman = simdi;
39      bipAcik = !bipAcik;
40    }
41    sesli = bipAcik;
42  }
43
44  if (sesli != sesCaliyor) {                // yalnızca değişince çal ya da sustur / switch only on change
45    sesCaliyor = sesli;
46    if (sesli) tone(BUZZER, 2000);
47    else noTone(BUZZER);
48  }
49}

There are two things to notice in the code. First, we gave pulseIn() a 30 ms timeout; if no echo comes back, the code doesn't wait forever and treats the distance as 400 cm. Second, tone() is only called when the sound state changes, so the buzzer isn't restarted on every pass and doesn't crackle. To take the project further, try showing the distance on an I2C LCD or OLED display and adding a warning bar of green, yellow and red LEDs.

Common mistakes when choosing and building projects

Which project suits you? Quick picks by interest

Once you've worked through all 30 projects in the list, you'll have used almost every basic building block of Arduino: digital and analog input and output, PWM, I2C, timing, motor control and state machines. To see what each sensor is for, take a look at the Arduino sensors guide as well. In the BlueGrays app you'll find most of these ideas, from LED Blink to the Obstacle-Avoiding Robot and from the Smart Irrigation Station to the ESP32 web server, with step-by-step circuit diagrams and ready-made code, so you can start right away with a project that matches your level.