Local grids, rotated grids, polar grids, and grid-aware component placement address a long-standing problem in PCB layout: a single global grid is not always practical for a board that combines different mechanical and electrical structures.

Figure 1 | A rectangular Cartesian grid, a rotated grid, and a polar grid used on the same PCB.
For a conventional rectangular PCB, one global grid is usually sufficient. However, layouts that include fine-pitch BGA regions, angled connectors, circular LED arrays, or multiple component pitches can make a traditional grid difficult to use. Designers often have to switch the global grid repeatedly or rely on coordinate calculations, copy-and-rotate operations, and array tools to complete the placement.
KiCad 11 introduces a different approach: a grid is no longer only an editor setting. It can become a design object placed on the PCB and saved with the project.
Grid Items Define Local Grid Regions
The KiCad 11 PCB editor adds Grid Items, which can be understood as local grids or subgrids. Designers can place multiple grid objects in specified areas of the PCB and configure each one independently. Available parameters include grid type, spacing, coverage area, rotation angle, priority, and major grid intervals.
The original global background grid remains available outside these regions. As a result, one board can combine a coarse global grid with a fine BGA grid, a rotated grid for an angled module, and a polar grid for a circular placement area.

Figure 2 | Demonstration of creating a local grid and adjusting its coverage area and parameters.
Because each local grid has its own definition, the grid can match the structure of the region being designed instead of forcing every part of the board to use the same coordinate system. This is particularly useful when a PCB combines electrical placement constraints with mechanical features that are not aligned to the main board axes.
Cartesian and Polar Grid Types
Rotatable Cartesian Grids
A Cartesian grid is the familiar X/Y square grid. In KiCad 11, a local Cartesian grid can use different spacing values and coverage limits for the X and Y directions. It can also have its own orientation.
This allows an angled connector, board-edge module, or functional daughterboard to use a local coordinate system aligned with its physical orientation. Components can snap to the local axes rather than to the global horizontal and vertical directions, making placement and alignment more direct.
A rotated grid is useful when the component pitch or mechanical reference is regular within a local region but does not align with the rest of the PCB. Instead of compensating manually for the rotation of the region, the designer can define the appropriate grid orientation once and continue placing objects within that coordinate system.
Polar Grids for Circular Layouts
A polar grid is defined by radius and angle. Its parameters can include the radial range and increment, angular range and increment, grid center, and overall rotation direction.
This grid type is well suited to LED rings, rotary knobs, encoder panels, circular sensor arrays, ring-shaped key layouts, radial connectors, and circular PCBs. Components can be positioned according to both their distance from the center and their angular location.

Figure 3 | A circular PCB layout in which different regions use independent grid directions and spacing values.
The polar grid is not merely a temporary set of reference lines. It is a native object in the KiCad PCB file. It can be selected, moved, rotated, edited, and locked, and it is saved together with the .kicad_pcb file.
This distinction is important for repeatability. A temporary editor setting mainly reflects the current user's working method, whereas a saved grid object records how a specific region of the PCB is intended to be laid out.
Grid-Aware Placement Automatically Adjusts Component Orientation
Snapping the cursor to a local grid is useful, but it does not fully solve the placement problem. KiCad 11 also adds grid-aware placement, which connects local grid behavior with footprint placement.
When a footprint is moved or placed, KiCad identifies the local grid that is active at the current position and adjusts the footprint orientation according to that grid. In a rotated Cartesian grid, the footprint aligns with the local coordinate axes. In a polar grid, kicad footprints can rotate according to the radial direction at its current location.
As a component is moved around a circular path, its orientation changes with its position. This is especially valuable for circular LED arrays, ring-shaped sensor layouts, and components arranged around knobs or other mechanical centers.

Figure 4 | Components automatically rotate to follow the active local grid.
When an object crosses from one grid region into another, its snapping behavior and placement orientation can change automatically. A workflow that previously required repeated copy, rotate, angle-entry, and position-check operations can instead become a more direct drag-and-place process.
Which Grid Takes Priority When Regions Overlap?
Multiple local grids can overlap. KiCad uses the Priority setting to determine which grid is active at a given position:
- A local grid with a higher priority value takes precedence.
- If two grids have the same priority, the grid with the smaller coverage area and more specific definition takes precedence.
- The original global background grid serves as the lowest-priority fallback.
For example, a designer can define a 1 mm grid for the entire board and place a higher-priority 0.1 mm local grid around a BGA. When the cursor enters the BGA region, KiCad automatically uses the fine grid. When the cursor leaves that region, it returns to the global grid without requiring manual switching.
The same principle can be applied to a board containing several areas with different placement requirements. Priority makes it possible to define broad default behavior while adding more specific rules where finer control is needed.
Practical Layout Workflows
- Mixed component pitches: Different regions of the PCB can use the spacing that best matches their components, reducing repeated changes to the global grid.
- Angled modules and edge interfaces: Rotated local coordinate systems allow placement and alignment to follow the orientation of the object.
- Circular PCBs and ring arrays: Components can snap by radius and angle while automatically adjusting orientation around the center.
- Mechanical and cosmetic layouts: Buttons, indicators, mounting holes, and contacts can be arranged efficiently around a mechanical center.
- Team collaboration: Because local grids are stored in the PCB file, the placement intent is shared with the project instead of remaining only in one engineer's temporary editor settings.
These use cases do not eliminate the need for careful mechanical and electrical review. They reduce repetitive placement operations and provide a coordinate system that better reflects the geometry of each region.
Current Limitation: Local Grids Primarily Support Placement
Local grids should not be interpreted as an automatic polar routing system. In the current implementation, their main purpose is cursor snapping and object or footprint placement.

Figure 5 | An early development experiment combining local grids with routing. This image illustrates a possible future direction; local-grid routing support is not complete in KiCad 11.
Interactive routing does not yet fully understand local grid geometry. The development experiments suggest a possible future in which a grid could influence not only where components are placed, but also the directions in which traces advance. That capability would be particularly interesting for circular or mechanically constrained boards, but it should not be treated as a completed KiCad 11 feature.
A Small Feature That Changes the PCB Editing Model
Traditional EDA software often treats the grid as a user-interface state. It helps the current user place objects, but it is not necessarily part of the PCB design itself. KiCad 11's Grid Items change that relationship by turning local coordinate systems into native board objects.
A Grid Item has a position, coverage area, orientation, parameters, and priority. It can also be shared with the rest of the project. This allows a grid to carry design intent, such as indicating that a region requires fine-pitch placement, that a module is rotated by a particular angle, or that components should be arranged radially around a defined center.
For a standard rectangular PCB, this may appear to be a relatively small convenience feature. For circular boards, mixed-pitch designs, angled interfaces, and mechanically complex layouts, however, multiple saved grid systems can significantly reduce placement overhead and improve consistency across the design team.
By making grids persistent, local, and aware of component orientation, KiCad 11 brings the coordinate system closer to the physical and functional structure of the PCB. The result is a more flexible placement workflow without requiring every region of the board to conform to one global grid.