What Is A CubeSat? (Aerospace Specs & Guide)

A CubeSat is a small satellite built around standard size units, with 1U measuring a nominal 10 × 10 × 10 cm. Its compact form does not make it simple: mission goals, spacecraft design, testing, and launch rules all matter. This guide explains common sizes, design limits, student preparation, and the steps that help a project move toward flight.

A CubeSat can look like a small box on a diagram. In practice, it is a spacecraft, its payload, and a set of interfaces that must work together. A design can fit the nominal size and still fail to meet a deployer’s limits or launch safety rules.

I use one question to keep a student project grounded: “What must this satellite do, and what evidence will show it can do it safely?” The answer helps connect classroom skills to real design choices.

CubeSat overview: mission classes, standards, and launch constraints

A CubeSat is a small spacecraft built to a modular size standard. The standard makes it easier to design deployers and plan spacecraft dimensions, but it does not make every CubeSat identical. The mission, deployer, launch provider, and current technical documents determine which requirements apply.

The CubeSat Design Specification (CDS), published by Cal Poly, describes common form factors and design expectations. NASA’s CubeSat Launch Initiative (CSLI) offers a path for eligible U.S. educational and nonprofit teams to seek launch opportunities. For any mission, the selected launch provider’s current requirements govern acceptance.

What do 1U, 3U, and other CubeSat sizes mean?

“U” means one CubeSat unit. A 1U spacecraft has a nominal envelope of 10 × 10 × 10 cm. A 3U spacecraft has a nominal envelope of 10 × 10 × 30 cm. Other common configurations add units, but the exact permitted shape depends on the applicable CDS revision and deployer.

These are nominal spacecraft dimensions, not a guarantee of fit. Rails, protrusions, tolerances, and deployer design can affect the allowed external envelope. Do not scale a design from a drawing alone. Check the applicable CDS revision and the launch provider’s interface-control document (ICD), which defines how the spacecraft must fit and connect to its deployer.

What determines CubeSat mass and launch eligibility?

There is no single maximum mass that applies to every CubeSat launch. The permitted mass depends on the spacecraft’s unit count, deployer, launch provider, and mission-specific limits. A spacecraft that meets a size target is not automatically eligible to fly.

Before choosing a design, confirm the current requirements for:

• Spacecraft dimensions, mass, and center of gravity
• Deployer interfaces and allowable protrusions
• Electrical and mechanical connections
• Safety documentation and hazardous materials
• Testing, delivery dates, and launch integration

The provider’s current documents take priority over generic classroom guidance. Treat them as design inputs from the start, not final paperwork.

CubeSat design: subsystems, budgets, and verification

A CubeSat is a collection of linked systems that must support one mission. Common subsystems include structure, power, communications, onboard computing, attitude control, and the payload. A design budget tracks limits such as mass, electrical power, data, and available volume so that teams can spot conflicts early.

How do teams turn a mission idea into a design?

Start with a mission objective: what should the spacecraft observe, measure, or demonstrate? Turn that goal into clear requirements. For example, a requirement might set a target for how often a payload must collect data. Each requirement should be testable, so the team can later show whether it has been met.

Then build and update four basic budgets:

• Mass: Estimate the mass of each part and leave room for uncertainty.
• Power: Track what the spacecraft produces, stores, and uses in each operating mode.
• Data: Estimate how much information the payload creates and how the spacecraft will store and send it.
• Volume: Check that parts fit within the spacecraft and deployer limits.

A change in one budget can affect the others. A larger payload may use more power, create more data, or leave less space for communications hardware. I encourage teams to record assumptions and revise budgets as measured component data replaces early estimates.

What tests are needed before launch?

Verification is the documented process of showing that a design meets its requirements. Teams may use analysis, inspection, or tests, depending on the requirement. A test plan should identify the item being tested, the method, the pass criteria, and the records the team will keep.

Launch environments can include vibration and shock. Teams also need to address electromagnetic compatibility, which concerns whether electrical systems interfere with one another, and launch safety requirements. The actual test levels and acceptance limits come from the selected provider’s current documents. A classroom test or generic test value cannot replace those limits.

Degree curriculum and technical requirements for CubeSat design

CubeSat work draws on several engineering fields. Students do not need to master every subsystem before joining a team, but they benefit from a base in mathematics, physics, programming, and engineering design. Course names and entry requirements vary by college, so check each institution’s program information.

What should students study?

A useful preparation path includes:

• Calculus and physics for modeling motion, forces, and electrical systems
• Programming for data handling, embedded systems, or mission operations
• Introductory engineering design for requirements, trade-offs, and testing
• CAD, electronics, or systems engineering for hands-on project work

Students can build experience through courses, supervised labs, design clubs, or faculty-led teams. Before selecting an engineering degree, check the school’s institutional accreditation status through recognized U.S. accreditation resources. For an engineering program, also check whether the specific program is accredited by the ABET Engineering Accreditation Commission (EAC), where applicable. Accreditation applies to a program, not automatically to every course or project.

How does a student join a CubeSat team?

Look for a faculty-led project and ask what roles are open, what time commitment is expected, and what training is required. A team may need help with software, mechanical design, electronics, payload testing, documentation, or outreach. A student can contribute without already knowing every spacecraft term.

Ask how the team manages safety, design reviews, and testing. A well-supervised project should explain who approves technical changes and how students learn to handle hardware responsibly. Course sequences, admissions standards, and GPA thresholds differ across institutions; verify them with the department rather than assuming one rule applies everywhere.

Academic success: project teams, testing, and student experience

A student CubeSat project can connect coursework to a complex engineering task. The experience is most useful when students have defined roles, supervision, and a record of their work. A flight opportunity can be valuable, but it is not guaranteed and does not replace a sound learning process.

Illustrative project scenarios: how design choices affect a mission

The examples below are design exercises, not reports of specific flown spacecraft. They show how a team might use requirements and provider documents to avoid common planning mistakes.

Scenario 1: A 1U sensor demonstration. A student team wants to collect a small set of sensor readings. It first checks whether the payload, computer, power system, and communications hardware fit within the applicable envelope. The team then estimates power use and data volume. If the sensor needs more space or power than expected, the team must revise its design or mission goal.

Scenario 2: A 3U payload mission. A larger form factor may provide more room for a payload or supporting systems, but it also raises new design questions. The team checks the deployer’s exact envelope, mass limits, interface requirements, and delivery schedule. It then plans testing and records how each requirement will be verified.

Scenario 3: A design that fits but is not ready to fly. A spacecraft meets its nominal dimensions, but the team has not completed required safety documents or provider-specific tests. The project may face delay or may not be accepted for that launch opportunity. The lesson is practical: check launch conditions while the design can still change.

Across all three scenarios, the key step is the same: confirm mission and launch requirements before committing to a design.

Mission-development workflow: from idea to launch review

A CubeSat mission moves through linked stages. A team develops its technical design, checks it against launch conditions, and records evidence of compliance. Schedules, funding, testing, and reviews can change along the way, so teams should revisit assumptions at each stage.

1. Build foundations. Study relevant math, physics, programming, and engineering design. Gain experience with tools such as electronics, CAD, or embedded systems.
2. Join a supervised team. Define the mission objective, users, payload, and applicable CDS revision. Identify a potential launch path and review its requirements early.
3. Design and verify. Write requirements, develop subsystem designs and budgets, and define how each requirement will be checked. Plan integration, testing, safety documentation, and provider reviews.
4. Document and learn. Record individual contributions, test results, design changes, and lessons learned. Use that evidence when seeking internships or further study in spacecraft systems, avionics, payloads, or mission operations.

The most important early check is whether the mission, schedule, and budget match the launch opportunity. A spacecraft that fits is only one part of launch readiness.

Career pathways in small-satellite engineering

Small-satellite projects can help students explore engineering work, but they do not guarantee a job, degree credential, or salary. Career outcomes depend on a person’s skills and experience, the quality of project supervision, and the labor market. A clear record of what you designed, tested, or analyzed is more useful than simply listing a project name.

Relevant areas include spacecraft systems, mechanical design, avionics, embedded software, payload development, testing, and mission operations. Students can strengthen their experience by keeping design notes, test plans, code samples where appropriate, and concise summaries of their contributions. Protect restricted project information and follow team rules when sharing technical work.

FAQ: CubeSat sizes, requirements, and student preparation

These answers cover common questions about CubeSat dimensions, mass, launch rules, and education. Use them as a starting point, then confirm technical details in the current CubeSat Design Specification and the selected launch provider’s documents. Requirements can differ between missions and launch opportunities.

What does “1U” mean in a CubeSat?
One U is a nominal size unit of 10 × 10 × 10 cm. The permitted spacecraft envelope depends on the applicable standard revision and deployer.

How big is a 3U CubeSat?
A 3U CubeSat has nominal dimensions of 10 × 10 × 30 cm. Its allowed external dimensions depend on deployer rules and tolerances.

Is there one maximum CubeSat mass?
No. Allowed mass depends on the spacecraft’s unit count, deployer, launch provider, and mission requirements. Check the current interface documents.

Does a CubeSat that fits the standard automatically qualify for launch?
No. Teams must also meet provider-specific limits for interfaces, safety, testing, documents, and schedule.

What is the CubeSat Design Specification?
The CDS is a Cal Poly document that describes CubeSat form factors and related design guidance. Use the revision that applies to your mission.

What is a launch provider’s interface-control document?
An ICD describes the physical, electrical, and other interfaces between a spacecraft and launch hardware. The provider’s current ICD helps define what it will accept.

Which subjects help prepare me for CubeSat work?
Calculus, physics, programming, and introductory engineering design are useful foundations. CAD, electronics, and embedded systems can also help, depending on your role.

Can a high school student join a CubeSat project?
Some projects may welcome advanced secondary students, but access and responsibilities vary. Contact the faculty lead and follow the project’s supervision and safety rules.

Does working on a CubeSat guarantee a job in aerospace?
No. A project can build relevant skills, but employment depends on many factors, including experience, qualifications, and available roles.

Where should a team confirm final launch limits?
Check the current CubeSat Design Specification, the deployer documentation, and the selected launch provider’s safety and interface documents. Provider requirements govern acceptance.

(This article was written by one of our staff writers, Nathan Sterling. Visit our Meet the Team page.)