Documentation
Go to AppSign InSign Up
    Getting Started
    • Introduction to Flux
    • What is Flux?
    • Quick Start
    • The Flux Method
    • Creating an Account
    • Flux for Organizations
    • Setting Up Your Browser
      • Mouse & Trackpad
      • Multi-Screen Operation
      • Keyboard Shortcuts
    • Your First PCB in Flux
      • DFM & Export
      • PCB Layout & Routing
      • Project Setup
      • Schematic
      • Export & Manufacturing
    • KiCAD to Flux
      • Layout
      • Parts & Libraries
      • Schematics
    • Eagle to Flux
    • EasyEDA to Flux
    • Upverter to Flux
    • Altium to Flux
    • Getting Help
    Tutorials
    • Tutorials
    • Getting Started With Flux
      • Customizing Flux
    • Flux Use Cases
      • AI Architecture Design
      • AI Component Research
      • AI Design Reviews
      • AI Testing & Debugging
      • AI Auto-Layout
      • Generative AI
    • Start Learning Flux, No Matter Your Skill Level
      • Advanced Designer
      • First Time Designer
      • Intermediate Designer
    • Power Regulator
      • 1 – Part Selection
      • 2 – PCB Layout
      • 2 – Schematics
    • Routing
      • High-speed Routing
      • High Density Designs (HDI)
      • Working with Polygons
    • Adding Components to the Library
      • Publishing Components to the Library
      • Creating Components from Scratch
      • Importing Components
      • Working with Footprints
      • Working with Symbols
    • What is a Module?
      • Module Design Best Practices
      • Creating Modules
      • Using Modules
    • Generic Components
      • Creating a generic part
    • Copper Fills Tutorial
      • Creating Copper Cutouts
    • Board Outline Shape and Size
    • The Toolbar
    • Using Layout Rules
    • Intro to collaboration
    • Embedding a Flux Project
    • Reviewing component updates
    • Version Control Deep Dive
    • Custom Shapes
    • AI-Assisted Design with Flux
    • PCB Design Reviews (DRC)
    • Component Placement
    • Component Procurement
    • Multi-Layer PCB Design
    • Working with Ground Signals
    • Reusing Projects
      • Useful links
    Reference
    • Flux Context Menu
    • Calculator Tool
    • Change Project Name
    • Code Tool
    • Convert to component
    • Flux ACUs
    • Overview
    • Data Portability
    • Delete & Archive Projects
    • Design Rule Check (DRC)
    • Expressions
    • File Tool
    • FMEA Report Generation
    • Gerber Exports
    • Help Tool
    • Special Part Types
    • JEP30 PartModel Import/Export
    • Knowledge Base
    • Library Tool
    • Managing Units
    • Measuring Distances
    • Model Selection
    • Nets and Traces
      • Curved Traces
      • Impedance Control
      • Trace Width
    • Object Types
      • AssetNode
      • ControlNode
      • ElementNode
      • ElementTerminalNode
      • OutputNode
      • PropertyNode
      • RouteNode
      • RouteTerminalNode
    • Pads & Holes
    • Passive Component Consolidation
    • Layout Rules Reference
      • Layout Rules List
      • Object-Specific Layout Rules
      • Selector-Based Layout Rules
      • Layout Rules Inheritance & Precedence
      • Layout Rules Modifiers
    • Polygons
    • Comments
    • Cursors
    • Forking & Cloning
    • Copper Fills
    • Importing Schematics
    • Importing Components
    • Schematic Inspector
      • Assets Panel
      • Pricing & Availability Panel
      • Properties Panel
      • Simulation Panel
    • The Library
    • Project Launcher
      • New Blank Project
    • Layout Object Tree
      • PCB Object Types
    • Schematic Object List
    • The PCB Editor
      • Locking
      • Layer View Control
      • Positioning & Routing
      • Selecting Objects
      • Stackup Editor
    • Permission Tiers
    • Preloaded Examples
    • The Profile Page
      • Featured Projects
    • The Schematic Editor
      • Positioning & Wiring
    • Global Search
    • Sharing & Permissions
    • History & Version Control
    • Silkscreen
    • Simulator Tool
    • Star a Project (Favorite)
    • Vias
      • Smart Vias
    Copilot
    • Copilot Overview
    • Model Selection
    • Flux ACUs
    • Knowledge Base
    • Flux Context Menu
    • Calculator Tool
    • Code Tool
    • File Tool
    • Help Tool
    • Library Tool
    • Simulator Tool
    • FMEA Report Generation
    • Passive Component Consolidation
    FAQ
    • Schematic Editor
    • General FAQs
    • Flux and AI FAQs
    • PCB Editor FAQs
    • Parts and Modules
    • Pricing
    • Private and public projects
    • Data security and IP protection
    • When things go wrong: Errors and how to handle them
      • Lost connection
    Legal
    • Terms of Service
    • Privacy Statement
    • Main Services Agreement
    • Subprocessors

Reference

Nets and Traces

Reference

Nets and Traces


When creating traces for a PCB, often times you will need to increase or decrease the size of the traces for a specific net. This can be done either through the specific net itself or, if you need to apply the size change to several nets, using rulesets.

What Is a Net?

Nets are a collection of electrically connected nodes in PCB design software. They represent paths for electrical signals to travel between components on the board. Every terminal on a PCB design program is connected to a net, and (unless in the case of high frequency transmission lines) all points on a net should share the same voltage. Nets oftentimes are named for easy identification and organizational purposes. Nets are used to generate netlists, which is a list of all the electrical connections to each component in the design.

What is a Trace?

Whereas a net represents the logical collection of nodes with a shared electrical connection, a trace is the physical conductive pathways that actually connects the individual components. A single net may represent the electrical connection of multiple components all sharing a single voltage value. This net, however, would be composed of multiple traces.

Traces are typically made of copper and can vary in widths depending on the desired current carrying capacity.

Trace and Net Specific Rules

Flux contains other related rules that allow you to further customize the behavior of traces and nets, listed below. See the complete list of rules for further information and examples for using each.

  • Fill stitching density: creates vias in a ground or power net fill, known as fill stitching.
  • Fill stitching offset: allows for offsetting fill stitching.
  • Preferred trace width: allows for presetting trace-widths for easy toggling during routing.
  • Trace shape: defines the shape of a trace, either curved or arced.
  • Trace width: sets the width of a trace (or collection of traces).

Naming and Renaming Nets

To keep your design organized and make debugging easier, you can rename nets to something more descriptive than the default auto-generated names. In Flux, you can do this by selecting the net from the Object Tree, then updating the “Designator” field in the Inspector panel. Giving nets intuitive names (like VCC, GND, or UART_TX) makes it easier to apply rules, track signal paths, and communicate design intent with your team.

Deleting Traces

Whether you're cleaning up a few connections or doing a full reroute, there are two ways to delete traces in Flux:

Delete single traces

Click to select the trace, then press Del, or right-click and choose Delete.

Delete multiple traces using the Objects panel

Open the Objects panel on the right:

  • To remove all traces under a specific net, expand the net in the list, select the traces, and press Del.
  • To wipe out all traces, type "trace" in the search bar, select the first result, hold Shift, scroll down, select the last one, and press Del.

Previous

Model Selection

Next

Curved Traces