PCB Reverse
Engineering Services
Recover the files.
Keep your equipment running.
Turn a physical circuit board into schematics, a verified netlist, a BOM and agreed editable design files. For maintenance teams, OEMs and repair businesses facing missing documentation or obsolete electronics.
What does a PCB reverse engineer recover?
PCB reverse engineering reconstructs the electrical design of a printed circuit board from the hardware itself. It connects component identification and trace analysis to useful outputs: a schematic, connectivity netlist, bill of materials and, when included, editable PCB and manufacturing files.
The goal is a usable engineering baseline. A maintenance team may need a readable schematic to isolate recurring faults. An OEM may need replacement production files after losing supplier support. A redesign team may need to replace an obsolete processor while preserving connectors and mechanical fit. These outcomes require different scopes, even when they start with the same board.
PCB-Copy reviews the physical sample, requested outputs and acceptance tests together. We distinguish what can be recovered from what needs separate investigation, such as firmware, calibration data, unidentified devices or missing sections of a damaged board. Start with what you want the equipment to do next; we can then define a practical recovery package.
PCB reverse engineering software or an engineering service?
Both can support a project. Choose according to the information you have and the result you need to verify.
Use a tracing tool to organize visible evidence
Photo annotation and EDA tools can help your own engineer record components, follow visible traces and organize connections. They are useful when you have time to trace the board and can check the result. A photo overlay is a view of recorded surfaces; it does not reveal hidden copper, establish an unreadable component value or recover a chip program.
Define an engineering scope for the gaps
When you need inaccessible connections investigated, a manufacturing package reconstructed or a prototype checked against equipment, specify those tasks and the required physical samples. Send any existing annotations, netlists or partial drawings with their known limitations. Useful work already completed can narrow the remaining scope.
Already using KiCad or another EDA application? State the application and version, which source files you have and which format you need at handover. Format compatibility and any conversion work are confirmed during review.
Compare PCB reverse engineering software and tools →From a board to engineering records.
Open a file group to see what to request and how to review it. This is an illustrative example, not a customer project or a ready-to-manufacture design. Your written scope defines the actual files and checks.
01 Schematic & connectivity
design/schematic.pdf + agreed editable sourceconnectivity/netlist.csv + verification notes
A readable schematic explains the circuit. A netlist records connections. The following row illustrates how an unresolved connection can be recorded without presenting it as verified.
| Endpoint A | Endpoint B | Status | Next check |
|---|---|---|---|
| J1, pin 1 | F1, pin 1 | To verify | Compare with physical continuity evidence |
02 Fabrication & assembly
fabrication/gerber/ + drill files + stackup notesassembly/placement.csv + assembly drawings
Review the board outline, layer order, hole sizes and units with the fabricator. Assembly information should identify the reference designator, side, rotation and position. A photo overlay does not supply hidden copper or confirm material and impedance requirements.
Understand Gerber recovery and its limits →03 BOM & unresolved parts
components/bom.csv + identification notes
Useful columns include reference designator, quantity, value, package, manufacturer part number, identification evidence and unresolved questions. Separate an identified original from a proposed substitute; neither a similar marking nor a matching footprint establishes compatibility.
See what belongs in a recovered BOM →04 Revision & acceptance records
release/file-manifest.csvverification/review-notes.pdf + agreed test records
The manifest ties the delivered files to one revision. Acceptance records state what was checked, the reference used and any open items. A prototype functional test, firmware recovery and product qualification each need their own agreed scope.
Review the verification scope →Editable planning template · No customer data · No upload or signup
Give your project a clear starting point.
Choose your requirements to create a brief you can download or add to the enquiry below. The suggested route helps frame a discussion; sample inspection and a written quote determine feasibility, price and timing.
Schematic & BOM recovery
Deliverables to discuss
Next useful step
Inputs and checks to confirm
View or edit your project brief
Changing a selection rebuilds this summary. Add project-specific notes in the enquiry form.Selections stay in this browser. Nothing is sent until you submit the enquiry.
Define the files before defining the price.
A complete-looking folder can still be unusable if the format, revision or test evidence is unclear. Agree the deliverables by name, including which files your own engineer or manufacturer needs to open.
Schematic and connectivity netlist
The schematic turns physical connections into a readable circuit document, with consistent reference designators and useful functional groupings. The netlist records which pins and nodes connect. Request a PDF for review and the agreed editable source for future changes. Mark unresolved values or connections explicitly so your team can separate verified information from items still requiring investigation.
BOM and component identification
A useful BOM links each reference designator to its value, package and identified manufacturer part number. Unreadable markings, custom parts and discontinued devices need attention before procurement. Distinguish an identified original component from a proposed alternative; a purchasing substitute may require electrical and firmware changes. Include obsolescence notes when continued production is the purpose of the project.
PCB source and fabrication data
When reproduction is included, define the native PCB file format together with Gerber, drill, placement and mechanical outputs. Your fabricator also needs the relevant layer and manufacturing requirements. Gerber data describes manufacturing artwork; it is not a substitute for a logically organized schematic. Confirm the CAD tool and version before recovery starts to avoid a handover your team cannot edit.
Verification records and optional prototypes
Specify how the recovered data will be checked and what evidence accompanies delivery. This may include netlist checks, inspection results and agreed functional measurements for a prototype. A build and its test fixture are separate project items unless expressly included. Acceptance should describe the functions and interfaces checked, rather than rely on the phrase “tested OK.”
Firmware remains a separate scope. A reconstructed PCB does not automatically reproduce the program, device configuration or calibration that makes a product work. Check IC unlock and firmware recovery feasibility.
Reverse engineering, PCB copy or redesign?
The names are sometimes used interchangeably. Compare the actual deliverables and acceptance criteria instead. A request for “the same board” should explain whether you need files, assembled units or a supported replacement design.
| Your purpose | Starting scope | What to confirm |
|---|---|---|
| Understand or troubleshoot | Schematic, netlist and BOM recovery | Readable drawings, unknown components and diagnostic priorities |
| Reproduce an existing layout | PCB copy and manufacturing files | Parts availability, firmware source, layer structure and production tests |
| Replace obsolete components | Reverse engineering followed by a defined redesign | Compatible interfaces, replacement parts and prototype validation |
| Restore a programmed device | Board review plus separate firmware feasibility | Exact device revision, data required and permitted sample handling |
Existing design files may change the route. If you already have complete, usable manufacturing data, send a description of that package during the initial review. The missing work might be component sourcing or production preparation rather than full reconstruction. Defining that distinction early keeps the quote aligned with the real problem.
A process with decisions you can review.
Clear checkpoints reduce surprises around samples, scope and completion. Review the sample plan before shipping an irreplaceable board.
Assess the board and intended outcome
Share both-side photographs, approximate dimensions, known layer count, board condition and the equipment it belongs to. Explain whether the priority is repair, reproduction or redesign. Identify firmware needs and any working reference. This first review establishes what further information or physical inspection is needed before the job can be accepted.
Agree confidentiality, samples and scope
Arrange an NDA before sharing sensitive files when required. Confirm the number of samples, shipping arrangements and permitted handling. Multilayer analysis may require removing components or exposing layers; any destructive work needs an agreed sample plan. The written quote should identify deliverables, formats, exclusions, milestones and the acceptance test.
Document, identify and reconstruct
The engineering work connects a physical inventory with the recovered circuit: record board features, identify components, trace connectivity and organize the schematic and netlist. Hidden connections and damaged areas require particular attention. Keep open questions visible so a missing component value or uncertain connection is resolved through evidence rather than silently carried into the files.
Verify the agreed result and deliver
Check the reconstructed data against the sample and complete the agreed prototype or functional checks where included. Review differences, unresolved items and test limitations before accepting the package. Final delivery should make the revision and file formats clear, so your team can move into maintenance, procurement or the next design stage without guessing which files are current.
What “verified” should mean for your board.
Electrical connectivity, component identification and equipment behavior are related checks, but they answer different questions. A successful continuity check alone does not prove that a replacement controller will run your machine.
Connection and component checks
Compare the recovered netlist with the physical interconnections. Check reference designators, device pinouts, power nets and connector assignments, especially under fine-pitch parts or across internal layers. Record uncertain component identities and values. A clear exception list is more useful than treating every recovered detail as equally certain.
Function and system checks
Define the input conditions, loads, interfaces and expected outputs for prototype testing. Timing, analog performance, thermal behavior and firmware configuration may affect the result. A working reference board or equipment test setup can be important. Where the original board is dead, state which functions can be tested independently and which remain dependent on system-level validation.
For regulated or safety-critical equipment, agree the separate product qualification and approval work needed before use. Recovered design files or a working prototype do not, by themselves, establish the complete equipment's compliance.
An obsolete ARM board, recovered for redesign.
- Board
- 8 layers
- Components
- 610
- Project time
- 14 working days
A diagnostics OEM needed a usable design baseline for a medical instrument main board containing an obsolete ARM device. The published scope covered schematic recovery, netlist verification and BOM research. The resulting documentation gave the customer's engineering team a starting point for replacing the processor.
The example shows why the requested outcome matters: understanding the original circuit was part of preparing a redesign, not simply ordering another bare board. Your project will have its own sample condition, component risks and acceptance tests; the quoted schedule is based on that scope.
Read the full project exampleWhat affects PCB reverse engineering cost?
Schematic recovery + BOM
Typical listed lead time: 7–15 days. Confirm the accepted scope and start point in the written quote.
View all service starting prices →The starting price describes one service category. It does not include every possible board, a complete redesign, protected firmware recovery or a production run. A useful comparison between suppliers starts with the same deliverables, file formats and test coverage.
Layers and access: internal routing, buried or blind vias, dense BGAs and inaccessible connections can require additional analysis. A layer count alone cannot describe the full workload; board area and routing density also matter.
Parts and condition: component count, erased markings, custom devices, damage and missing parts affect identification and reconstruction. A second reference can reduce uncertainty, but the number and condition of samples must be reviewed for the actual board.
Depth of handover: schematic and BOM recovery is different from an editable PCB database, complete fabrication files, redesigned circuitry and a tested prototype. Ask the quote to separate those items and state any dependencies between them.
Acceptance and logistics: required fixtures, equipment access, component procurement and sample transport can influence the overall schedule. Confirm whether stated timing covers engineering only or also prototype production and delivery.
Our applicable project terms include a 50% deposit, the remaining balance after the agreed test, and a full refund if the accepted work cannot be completed. Confirm the accepted deliverables and test criteria with the quote so those terms refer to a clear, shared definition of completion.
Make your enquiry easier to answer.
Start with the information available; unknown fields are acceptable. Do not remove components or ship your only working board before discussing the sample plan.
Photograph both sides in focus, including connectors, labels and the complete markings on major ICs. Give the board dimensions and describe damage or previous repair work. Explain the machine's role, the symptom or supply problem, and the output your team needs to receive. If you have drawings, Gerbers, manuals or a partial BOM, describe them before sending confidential material.
Your preparation checklist
0 of 5 details prepared
PCB-Copy is based in Bao'An, Shenzhen, China, and handles enquiries from customers worldwide. Judy is the project contact. Request an NDA before sharing sensitive files, confirm the shipping details directly, and explain the basis on which you own or are authorized to reproduce the board. Read our legitimate use policy.
PCB reverse engineering FAQs
Specific answers for engineers and buyers planning a recovery project.
What does a PCB reverse engineer do?
A PCB reverse engineer reconstructs a board's electrical connections, component information and design documentation from physical hardware. The agreed output may include a schematic, netlist, BOM, editable CAD files and fabrication data. This is different from repairing a single fault: the purpose is to create information your team can use for maintenance, reproduction or a controlled redesign.
Can you reverse engineer a PCB without the original schematic?
Yes. Missing schematics are a common starting point. Clear photographs help with the initial review, but a physical sample is normally required to identify connections and inspect hidden features. Existing files, partial drawings and equipment manuals are still useful: they reduce uncertainty and help define the expected behavior. Tell us whether the sample works before agreeing the recovery and test plan.
How much does PCB reverse engineering cost?
Our published starting price for schematic recovery plus BOM is $400, with a typical listed lead time of 7–15 days. That is not a fixed price for every board or a complete replacement product. Layer structure, component density, damage, requested files, firmware and prototype testing affect the written quote. Production, shipping and other project items should be confirmed separately.
Can a multilayer PCB be recovered without destroying it?
The sample plan depends on how its connections can be accessed and verified. A board with hidden layers, buried vias or inaccessible features can require component removal or destructive layer analysis. Do not assume that your only working board will be returned intact. Tell us what samples you have, and agree the permitted analysis method and sample count before shipment.
Does schematic recovery include MCU or FPGA firmware?
No. A schematic describes hardware connectivity; it does not contain the program, configuration or calibration stored in a device. Firmware recovery needs its own feasibility assessment using the exact marking, package, revision and protection state. We can review this alongside the board project, but it should be separately identified in the scope and acceptance criteria.
Can you replace obsolete components or redesign the board?
Recovered files can provide the baseline for an obsolescence redesign. A replacement component must be assessed for electrical limits, pinout, timing, software dependencies, availability and mechanical fit. A similar part number is not enough. Tell us which parts are unavailable and which interfaces must stay unchanged, so the quote can distinguish documentation recovery from redesign and prototype validation.
Which design files will I receive?
The written scope identifies the exact package. Typical outputs are schematic PDF and agreed editable source, connectivity netlist, BOM with manufacturer part numbers where identified, and optional Gerber, drill, placement and native PCB files. Agree the CAD software and version before work begins. Also specify whether you need a prototype and which inspection or functional-test records must accompany the final handover.
How do I start under an NDA?
Contact Judy at Judy@4PCBA.com before sending confidential files if an NDA is required. Start with your project purpose, general board description and the documents you need. Confirm the confidentiality terms, sample handling, accepted work and test criteria before shipment. PCB-Copy works on boards you own or are authorized to reproduce; the project scope must respect that authorization.
Make the next project decision with confidence.
PCB Repair vs Replacement: A Guide for Legacy Equipment
A failed circuit board creates two decisions: how to restore the machine now, and how to support it when the next board fails. Compare the options before committing to a repair or a replacement project.
BIN vs HEX Firmware Files: What Your Replacement MCU Needs
A firmware file is only useful when the destination, memory map and programming requirements are understood. Learn what BIN and Intel HEX describe, and what else a replacement microcontroller may need.
PCB Clone Not Working? Check Hardware, Firmware and Test Conditions
A board that looks identical can behave differently. Organize the evidence before changing parts or rewriting firmware, so the next engineering step addresses the actual mismatch.
Put your board in front of the right conversation.
Send your board details or use the project planner above to prepare a brief. Judy will help confirm feasibility, sample handling, deliverables, timing and a written quote.
Your contact: Judy
Judy@4PCBA.com
Bao'An Shenzhen China
Service information published by PCB-Copy · Updated
Back to top ↑