Learn Altium Develop by doing.
Start with the job in front of you.
Ask Atlas, your virtual applications engineer, or choose the learning path that works for you.
Hundreds of years of Altium applications experience. One question away.
QUICK WINS
Pick a job. Make progress in 15 minutes.
Choose something close to what you're working on now. We'll show you how to do it in Develop, what success looks like, and where to go next.
Atlas is here whenever you need help.
Set the rules before routing starts.
A missed clearance, width, or length constraint is much easier to deal with before the board is routed than after.
What you'll do
Create a net class with clearance, width, and length constraints. Route it, then use Constraint Manager to verify the result.
Working with DDR4 or SerDes? Take it further with an xSignal class.
You'll know it worked when
Your routed design satisfies the constraints you intended to enforce.
You'll use:
Go further. See how the same constraint definitions can stay with the design when someone else needs to review your work.
Let the router do more of the work.
Routing gets tedious fast when every obstacle, matched length, and differential pair becomes a manual cleanup job.
What you'll do
Route a bus using push-and-shove. Tune a length-matched group. Then route a differential pair while maintaining the constraints you've already defined.
You'll know it worked when
You've completed the routes without manually rebuilding every segment along the way.
You'll use:
Go further. Try the same exchange with a mechanical engineer working in their own MCAD environment.
Stop passing the board back and forth as STEP files.
A mechanical export only represents a moment in time. Move a connector or mounting hole and the exchange starts again.
What you'll do
Push your PCB to SOLIDWORKS, Inventor, Creo, Fusion, or NX. Make a mechanical change, then bring that change back into the PCB design.
You'll know it worked when
You can see the proposed mechanical change in the layout and decide how it should be applied without rebuilding the exchange from scratch.
You'll use:
Go further. Try the same exchange with a mechanical engineer working in their own MCAD environment.
Check the part before it becomes a problem.
A component can be electrically correct and still create trouble when it's time to build.
What you'll do
Place a component using Manufacturer Part Search. Open the BOM and inspect the available lifecycle, stock, and pricing information for the parts in the design.
You'll know it worked when
You can see sourcing context against your actual BOM while there's still time to make a design decision.
You'll use:
Go further. See how someone responsible for sourcing can review BOM information without working inside the PCB editor.
Get feedback on the design. Not a screenshot of it.
PDF markups, screenshots, and email threads lose the context that makes engineering feedback useful.
What you'll do
Publish the project, share it, and add a comment directly to the component, net, or location being discussed.
You'll know it worked when
The feedback stays connected to the design context and the version being reviewed.
You'll use:
Go further. Send the review to someone who would normally ask you for a PDF or screenshot.
Know exactly what you're sending to manufacturing.
Outputs, drawings, revisions, and last-minute changes make the end of the design cycle an easy place for versions to get crossed.
What you'll do
Configure an Output Job. Generate fabrication and assembly outputs plus a Draftsman drawing. Then create a release tied to the project state you're ready to send.
You'll know it worked when
You have a clearly defined manufacturing package associated with the revision you intended to release.
You'll use:
Go further. Share the released package with your manufacturer instead of sending another ZIP file with a note explaining which version is current.
Go deeper when you're ready.
Quick Wins get you moving. When you want the full story, follow a guided path or explore the complete resource library. Atlas is here when you need him.
GUIDED PATH
Prefer to learn step by step?
Follow Altium Develop from getting started through design, sourcing, review, and release.
Work through it in order, skip what you already know, or ask Atlas to explain anything along the way.
RESOURCE LIBRARY
Looking for something specific?
Explore technical articles, guidebooks, videos, webinars, and other resources across Altium Develop.
Search for what you need — or tell Atlas what you're trying to accomplish and let him help you find it.
Pick one mission.
Do it before you close this tab.
The best way to learn Develop is to put it to work.
Pick something that's already on your desk, something you've been meaning to learn,
or something that's been slowing you down.
One screen for the work. One for Atlas when you need him.