Electronics decoder
SMD Component Marking Lookup
Look up candidate SMD parts from a top marking and package context using the imported JLCPCB database.
Inputs
Results
- Candidate summary
- Waiting for input
- Confidence
- Waiting for input
Lookup context
Candidates
Candidate table
Reference rows
Use the SMD Component Marking Lookup when you have a broader SMD top mark and package context, not a guaranteed part number. The page is now organized around the imported corpus itself: how many rows were kept, how many lookup groups were built, and which package families dominate the current library.
Imported database
| Metric | Count | Meaning |
|---|---|---|
| Source rows | 694 | Rows read from the imported CSV corpus. |
| Kept rows | 176 | Rows that passed the marking-oriented filter. |
| Lookup groups | 174 | Canonical exact-lookup groups currently exposed by the loader. |
| Package families | 39 | Distinct package families represented in the imported corpus. |
| Alias terms | 47 | Alias rows preserved from the source library. |
| Ambiguous aliases | 0 | Alias keys that map to more than one lookup group. |
| Skipped rows | 518 | Source rows that were filtered out because they are not marking candidates. |
The current corpus is tracked as 174 lookup groups across 39 package families. That is the launch boundary: the page reports the imported corpus, it does not invent new matches.
Representative records
| Marking | Decoded result |
|---|---|
| 1AM|sot-23 | 1 candidate(s) found for 1AM in SOT-23. |
| 1N4148W|sod-123 | 1 candidate(s) found for 1N4148W in SOD-123. |
| 2L|sot-23 | 1 candidate(s) found for 2L in SOT-23. |
| 2N3904S|sot-23 | 1 candidate(s) found for 2N3904S in SOT-23. |
| 2N7002|sot-23 | 1 candidate(s) found for 2N7002 in SOT-23. |
| 2SC3356|sot-23 | 1 candidate(s) found for 2SC3356 in SOT-23. |
Top package families
| Package family | Rows |
|---|---|
| SOIC-8 | 35 |
| SOT-23 | 31 |
| SOIC-16 | 14 |
| LQFP-48 | 8 |
| LQFP-64 | 8 |
| LQFP-100 | 6 |
| SMA | 6 |
| SOIC-14 | 6 |
How the output is written
| Output field | Meaning |
|---|---|
| Preview visual | Schematic marking visual that reflects the current top mark and package context. |
| Candidate summary | Plain-language summary of the matched corpus rows. |
| Confidence | How strongly the imported corpus narrows the candidate set. |
| Segment breakdown | The top mark, package context, and candidate count written as separate fields. |
| Candidate table | Candidate parts, package family, device type, and evidence notes. |
| Reference rows | Imported source notes and limits that sit behind the candidate set. |
How to enter an SMD top mark
- Enter the visible top mark exactly as printed, including punctuation when it is part of the code.
- Choose the package context that matches the body footprint before trusting the candidate count.
- Read the candidate summary first, then inspect the candidate table and board context before making a part decision.
- Verify the logo and manufacturer data sheet before replacing the component.
What the lookup does not decide
- Confirmed part number, unless the package, logo, and documentation all agree.
- Electrical rating, pinout, or package equivalence beyond the visible candidate set.
- Authenticity or board-level suitability.
- Whether one candidate can be substituted for another without design review.
Sources and limits
Limits: This page covers only the imported reference set and the explicit alias rows preserved from the source data. It does not replace the original part marking, package drawing, manufacturer data sheet, or any electrical approval requirement.
Source corpus: JLCPCB Basic SMT Components.csv from rljacobson/JLCPCBBasicLibrary under CC BY 4.0; cross-checked against Part-DB-server, POETRY-SMALL-PARTS, and iCopy-X teardown notes for package and naming conventions; verified 2026-08-30.
- The imported database is a marking corpus, not a universal semiconductor catalog.
- Package family narrows the search, but it is still only one part of the decision.
- Use the board context, logo, and manufacturer data sheet before treating a candidate as confirmed.
- Do not treat the decoded output as a safety, procurement, or replacement decision.
Decode logic
- Normalize the top mark and package context, then narrow the candidate set to the imported database rows.
- Use only explicit short-mark aliases that are backed by a source row; do not invent new matches.
- Use the package family, logo, board context, and manufacturer data sheet to confirm the exact component.
FAQs
What does the candidate summary mean?
It shows how many parts matched the current top mark and package filter in the reference set.
Can package alone identify the part?
No. Package helps narrow the search, but logo, board context, and datasheet confirmation are still needed.
Why can one top mark have multiple candidates?
Short marking codes are reused across different manufacturers and part families, so the database keeps the ambiguity visible.