Default solder paste aperture is 0.7x the pad (49% of its area)

Open Beginner friendly
#4,800 1 comment 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

@zainrizvi0611-cmd is already working on this.

Since Oct 30, 2026.

  • #4801 by @DurandA — closed without merging
  • #4802 by @JohnNuwan — closed without merging
  • #5013 by @zainrizvi0611-cmd — open
  • #5199 by @Crodify — open
  • #5263 by @jeffrey-graham — closed without merging
  • #5491 by @Abse2001 — open

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
74/100
Issue type
Feature
Clarity
Clearly specified
Activity status
Active
Tech stack
typescript
Domain
backend

Research direction

Start with lib/components/primitive-components/SmtPad.ts and inspect how solderPasteMargin is used when no margin is supplied. Check existing SmtPad tests for default paste aperture behavior. Done when the default aperture matches the pad dimensions while an explicit negative margin still reduces it.

Written by the indexing model from the issue text.

Description

Without solderPasteMargin, SmtPad makes the paste aperture 0.7x the pad width and height (padSize * 0.7 in lib/components/primitive-components/SmtPad.ts). The paste then covers only 49% of the pad.

Footprint strings and imported parts never set a margin, so every SMD pad gets this. Example: an 0603 pad of 0.80 x 0.95 mm gets 0.56 x 0.67 mm of paste.

That is about half the usual paste, a risk of open joints and tombstoning, and nothing flags it. KiCad and Altium default to a margin of 0 (aperture = pad).

Proposal: default solderPasteMargin to 0. Pads that need less paste can still set a negative margin.

Related: #2896, #2945

Dominant language
TypeScript
Stars
61
Forks
256
Avg merge
20h 21m
Merged PRs (30d)
289

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from tscircuit/core

All issues in tscircuit/core

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.