Home/Printers/MakerBot

FDM / FFF

MakerBotA world of possibilities.

MakerBot's kit-printers origins led to assembled Replicator systems, Stratasys ownership and a later merger with Ultimaker.

01 / 03FDM / FFF
MakerBot Cupcake CNC
Bre Pettis / CC BY 2.0

Cupcake CNC

5printersin the collection
1technologyFDM / FFF
2009FoundedMakerBot

Explore. Inspect. Compare.

The MakerBot collection.

Compare generations

5 printers

Manufacturer reference

Where this maker fits.

Model documentation verified · References checked 2026-10-16

Official manufacturer reference
Technologies in this record
FFF
Applications in this record
Consumer
Material families
PLA
Entry type
Brand / historical brand
Documented model years
2009–2016

Different ways to make

The technology
behind the object.

MakerBot technologies represented in this collection.

Through the generations

Every generation
begins somewhere.

Open interactive history

Dates describe the event stated in the source, such as an announcement or product launch.

  1. 2009

    MakerBot and Cupcake

    MakerBot was founded in 2009 and introduced its first Cupcake printer.

  2. 2010

    Thing-O-Matic

    The next kit incorporated an automated conveyor build platform.

  3. 2012

    Replicator family

    The original Replicator launched at CES; Replicator 2 followed in September.

  4. 2013

    Stratasys acquisition

    Stratasys completed its acquisition of MakerBot on August 15.

  5. 2016

    Replicator+ launch

    MakerBot introduced Replicator+ and Replicator Mini+ on September 20.

  6. 2022

    Merger with Ultimaker

    The merger closed August 31 and was publicly announced as completed September 13. The combined company used UltiMaker.

Behind the collection

Details you can
trace to the source.

Early-machine narrative includes the cofounder's first-hand history. The original 2012 Replicator is distinct from the 2014 fifth-generation model.

View the manufacturer record
Sources & collection notes +

Historical means the machine is included for its place in the lineage. It does not by itself establish a discontinuation date or an end to support. Undocumented fields remain marked as not verified.