Embedded Basics

What Is an Embedded System? Definition, Features and Examples

Learn what an embedded system is, how it works, its main components and features, real examples, a short history, and why embedded systems matter today.

On this page
  1. What is an embedded system?
  2. How an embedded system works
  3. The main components of an embedded system
  4. Key features and characteristics of embedded systems
  5. Examples of embedded systems
  6. Types of embedded systems
  7. A short history of embedded systems
  8. Why embedded systems are important
  9. How embedded systems are programmed
  10. Embedded systems vs general-purpose computers
  11. Frequently asked questions

What is an embedded system?

An embedded system is a computer built into a larger device to do one specific job, or a small set of closely related jobs. It usually combines a processor, memory, and input/output hardware with software written for that one purpose. Unlike a laptop, it isn’t meant to run whatever programs the user installs.

The word “embedded” means the computer is built into something else. You usually don’t see it, and you don’t think of the product as a computer at all. A microwave oven, a car’s anti-lock braking module, a digital thermostat, a fitness tracker, and a Wi-Fi router all contain embedded systems. The user presses a button, turns a dial, or does nothing at all, and the embedded system handles the rest.

Embedded systems range from tiny to large:

  • A simple one might be a single 8-bit microcontroller in a TV remote, waking up only when a button is pressed.
  • A mid-range one might be a 32-bit microcontroller running a real-time operating system in a drone flight controller.
  • A complex one might be a multi-core processor running embedded Linux in a car’s infotainment unit or a network switch.

All of them are dedicated to a defined role inside a bigger product.

How an embedded system works

Most embedded systems follow the same basic loop: sense, decide, act.

  1. Inputs bring information in. This could be a temperature sensor, a button, a microphone, a radio receiver, or data arriving over a network.
  2. The processor runs firmware that interprets those inputs and decides what to do.
  3. Outputs carry out the decision. They might switch a relay, spin a motor, light an LED, update a display, or send a message.

A digital thermostat is a good example. A temperature sensor is read every few seconds. The firmware compares the reading with your setpoint. If the room is too cold, it switches a relay that turns on the furnace. It also updates the display, responds to button presses, and, if it’s a “smart” model, reports to an app over Wi-Fi. It does this continuously for years, with no one ever “opening” a program.

This close link to the physical world is what makes embedded systems distinctive. They don’t just process data. They measure and control real things, often on a deadline.

The main components of an embedded system

Processor

The processor runs the system’s software. Embedded designs use several kinds:

  • Microcontrollers (MCUs) put a CPU, flash memory, RAM, and peripherals on one chip. They’re the most common choice for small and mid-sized devices. See our guide to microcontrollers vs microprocessors for the details.
  • Microprocessors and application processors (MPUs) offer much more computing power but need external memory and storage. They’re used where a full operating system such as Linux is needed.
  • Systems-on-chip (SoCs) combine one or more processors with graphics, radios, and other blocks on a single chip.
  • FPGAs and ASICs implement custom hardware logic. They’re used where software alone isn’t fast enough or where very high volumes justify a custom chip.

Memory

Embedded systems typically have two kinds of memory:

  • Non-volatile memory (usually flash) holds the program and keeps it when power is off.
  • RAM holds working data while the system runs.

Small microcontrollers may have only a few kilobytes of RAM, so code size and memory use matter a great deal.

Inputs, outputs and peripherals

Peripherals connect the processor to the outside world. Common ones include:

  • General-purpose I/O pins
  • Analog-to-digital converters (ADCs) for reading sensors
  • Timers and PWM outputs for driving motors and LEDs
  • Communication interfaces such as UART, SPI, I2C, CAN, USB, and Ethernet
  • Wireless radios such as Bluetooth, Wi-Fi, or cellular

Power supply

Embedded systems can be powered by mains electricity, batteries, a car’s electrical system, or harvested energy. Voltage regulators, battery management, and low-power sleep modes are often central to the design, especially for battery-powered devices expected to run for months or years.

Software and firmware

The software in an embedded system is usually called firmware, because it’s stored permanently in the device and closely tied to its hardware. It might be:

  • A single loop running directly on the hardware (“bare metal”)
  • An application running on a small real-time operating system (RTOS)
  • A full embedded Linux system

Our article on firmware vs software explains where the line between the two terms sits.

Key features and characteristics of embedded systems

Embedded systems vary enormously, but most share these characteristics:

  • Dedicated function. The system is designed for a specific task. The washing machine controller runs wash cycles. It doesn’t browse the web.
  • Real-time behavior. Many embedded systems must respond within a fixed time. An airbag controller or a motor drive can’t afford to “lag.” Not every embedded system is hard real-time, but timing is usually a design concern.
  • Resource constraints. Processing power, memory, and storage are typically limited to keep cost, size, and power low. Developers often work with kilobytes, not gigabytes.
  • Low power consumption. Many devices run on batteries or must stay cool without fans, so efficiency is a priority.
  • Small size and low unit cost. Products made in large volumes are designed to use the cheapest hardware that does the job reliably.
  • Reliability and long life. Embedded systems often run unattended for years, sometimes in heat, cold, vibration, or moisture. Recovering automatically from faults (for example, with a watchdog timer) is common.
  • Interaction with the physical world. Sensors and actuators are central, not optional.
  • Limited or no user interface. Some have touchscreens, but many have only a few buttons and LEDs, or no direct interface at all.

Examples of embedded systems

Embedded systems are everywhere. A few examples:

  • Home: microwave ovens, washing machines, smart thermostats, smart speakers, TV remotes
  • Personal: fitness trackers, smartwatches, wireless earbuds, digital cameras
  • Automotive: engine control units, anti-lock braking systems, airbag controllers, infotainment systems
  • Medical: pacemakers, insulin pumps, infusion pumps, pulse oximeters, patient monitors
  • Industrial: programmable logic controllers (PLCs), robot controllers, motor drives
  • Infrastructure: routers, network switches, ATMs, smart meters, traffic signal controllers

For a fuller tour, see our guide to embedded system examples and applications. For an everyday walk-through, see real-life examples of embedded systems.

Types of embedded systems

Embedded systems are commonly grouped into four types by function:

  • Standalone: works on its own, like a microwave
  • Real-time: must meet timing deadlines, like an airbag controller
  • Networked: depends on a network connection, like a security camera
  • Mobile: portable and battery-powered, like a fitness tracker

They can also be grouped by complexity (small-scale, medium-scale, and sophisticated) or by the processor and software they use. Our article on types of embedded systems covers each category in detail.

A short history of embedded systems

Dedicated control computers are nearly as old as computing itself, but a few milestones stand out:

  • 1960s: guidance computers. The Apollo Guidance Computer, developed at the MIT Instrumentation Laboratory for NASA’s Apollo program, is often cited as one of the first modern embedded systems. It was a dedicated computer built into a spacecraft to handle navigation and control. Around the same time, military systems such as the Autonetics D-17B guidance computer for the Minuteman missile used dedicated computers in a similar way.
  • Early 1970s: the microprocessor. Intel’s 4004, released in 1971, was designed for a Busicom calculator. Putting a programmable processor on a single chip made it practical to add computing to everyday products.
  • Mid-1970s to 1980s: the microcontroller. Chips that combined a processor, memory, and I/O on one die, such as Texas Instruments’ TMS1000 family and later Intel’s 8048 and 8051, made embedded control cheap enough for appliances, toys, and cars. The 8051 architecture is still found in some products today.
  • 1980s and 1990s: cars and consumer electronics. Electronic engine control spread through the automotive industry, and microcontrollers moved into VCRs, phones, and household appliances. Real-time operating systems became a standard tool for more complex designs.
  • 2000s onward: 32-bit and connected. Low-cost 32-bit microcontrollers, especially those based on Arm Cortex-M cores, became mainstream. Cheap radios brought Wi-Fi and Bluetooth into small devices, and hobbyist platforms such as Arduino and Raspberry Pi opened embedded development to a much wider audience.
  • Today: IoT and on-device AI. Many embedded systems are now networked and receive over-the-air updates, and some run small machine learning models locally. Security and long-term maintenance have become central concerns.

Why embedded systems are important

Embedded systems are important because most computing in the physical world happens on them. They make products safer, more efficient, and more capable at low cost:

  • Safety: anti-lock brakes, airbags, and medical devices depend on fast, reliable embedded control.
  • Efficiency: motor controllers, smart thermostats, and battery management systems help reduce energy use.
  • Automation: factories, warehouses, and farms rely on embedded controllers to run machines precisely and continuously.
  • Connectivity: the Internet of Things is essentially a network of embedded systems.
  • Everyday convenience: many products people use daily would not work in their current form without them.

Because they’re invisible, embedded systems are easy to overlook. But a typical modern car alone contains dozens of electronic control units, and an ordinary home contains many more embedded processors across its appliances and gadgets.

How embedded systems are programmed

Embedded programming means writing software that runs directly on, and controls, a device’s hardware. Compared with typical desktop or web development, it involves working closely with registers, interrupts, timers, and peripherals, and paying attention to memory, timing, and power.

  • Languages: C has long been the dominant language for embedded work, and C++ is widely used too. Rust is gaining interest for its memory-safety guarantees. MicroPython and CircuitPython are popular for learning and prototyping on capable microcontrollers. Assembly is still used occasionally for very small or timing-critical code.
  • Software approaches: Simple devices often run bare metal, with a main loop plus interrupt handlers. More complex ones use an RTOS such as FreeRTOS or Zephyr to manage multiple tasks. The most capable run embedded Linux.
  • Tools: Developers use cross-compilers (code is built on a PC for a different target processor), vendor or open-source IDEs, hardware debuggers connected via JTAG or SWD, and test equipment such as oscilloscopes and logic analyzers.

Embedded systems vs general-purpose computers

A general-purpose computer, such as a laptop, desktop, or server, is designed to run whatever software its user chooses. An embedded system is designed around one fixed job. That difference shapes everything else: the hardware, the operating system (or lack of one), power use, cost, and how the system is updated. See our full comparison of embedded systems vs general-purpose computers, or read what a general-purpose system is for the other side of the comparison.

Embedded systems also have real trade-offs. They’re hard to upgrade, constrained by limited resources, and increasingly exposed to security risks. Our article on the advantages, disadvantages and challenges of embedded systems covers these in detail.

Frequently asked questions

What does “embedded” mean in computing?

It means the computer is built into a larger product as one of its parts, rather than being a standalone computer. The product’s purpose (cooking, braking, measuring) comes first, and the computer exists to serve it.

Are embedded systems programmed in C or C++?

Both are used. C remains the most common language in embedded development, especially on small microcontrollers. C++ is widely used on more capable chips and in larger codebases. Many projects use a mix, and Rust is a growing alternative.

What is embedded programming?

It’s writing software for embedded hardware: configuring peripherals, handling interrupts, reading sensors, driving outputs, and meeting timing and memory limits. The code usually runs without a desktop operating system and is compiled on a separate development computer.

What is the difference between IoT and embedded systems?

An embedded system is any dedicated computer inside a device. An IoT (Internet of Things) device is an embedded system that’s also connected to a network, usually to send data to or receive commands from other devices or cloud services. Most IoT devices are embedded systems, but many embedded systems aren’t connected to anything.

Do embedded systems have a future?

By most indications, yes. Cars, appliances, industrial equipment, medical devices, and energy systems keep adding electronics, and connected and AI-capable devices create new design and security work. The tools and languages will keep changing, but the need for dedicated computers inside products shows no sign of going away.

Keep exploring

Guides from other topics

All topics →