Altium NEXUS Documentation


Created: August 3, 2017 | Updated: July 28, 2018
Applies to Altium NEXUS Client versions: 1.0, 1.1, 2.0, 2.1, 3.0, 3.1, 3.2, 4 and 5
This documentation page references Altium NEXUS/NEXUS Client (part of the deployed NEXUS solution), which has been discontinued. All your PCB design, data management and collaboration needs can now be delivered by Altium Designer (with Altium Designer Enterprise Subscription) and a connected Altium 365 Workspace. Check out the FAQs page for more information.

Parent page: Schematic Commands

The following pre-packaged resource, derived from this base command, is available:

Applied Parameters: None


This command is used to add a new component to the current document.


This command can be accessed from the Schematic Library Editor in the following ways:

  • Choose Tools » New Component from the main menus.
  • Click the  button on the Utility Tools drop-down () of the Utilities toolbar.
  • Right-click and choose Tools » New Component from the context menu.


After launching the command, the New Component dialog will open. Use this dialog to give the component a suitable name. After clicking OK, a new component with this name will be created in the library and an empty component sheet is opened and made active in the main design window.

You are now set to proceed with defining the new component. To summarize, this involves the following steps:

  1. Define the component body using the various drawing objects available.
  2. Place the component pins.
  3. If you are creating a multi-part component, add the additionally required parts to the component and repeat the above steps to create the symbols for all parts in the component.
  4. Set the component's properties.
  5. Save the component sheet to save the component in the library.


  1. Schematic component library (*.SchLib) sizes are virtually unlimited and are only restricted by available memory.


Found an issue with this document? Highlight the area, then use Ctrl+Enter to report it.

Contact Us

Contact our corporate or local offices directly.

We're sorry to hear the article wasn't helpful to you.
Could you take a moment to tell us why?
200 characters remaining
You are reporting an issue with the following selected text
and/or image within the active document: