Soft Ip vs Hard Ip

Soft IP and hard IP are the two forms a licensed circuit block can come in: soft IP is portable source code that still has to be synthesized and laid out for the target process, while hard IP is a finished, process-specific physical layout ready to drop straight into a chip.

Design team needs a block it doesn't want to design from scratch
a CPU core, a PCIe controller, a PLL, an SRAM array
Choose the form the licensed block comes in
Soft IP: RTL source, synthesized fresh for this chip
hard IP: finished GDSII layout, already tied to one process
Tradeoff: portability and flexibility vs. guaranteed performance
the choice usually comes down to what the block actually is

This distinction solves the problem that not every circuit block benefits from the same kind of reuse, because some blocks need to flex with the design around them and others need to be proven correct down to the transistor. Soft IP ships as RTL — Verilog or VHDL source code describing behavior — which means it still has to go through synthesis, place-and-route, and timing closure on the target process just like internally-designed logic, giving the integrating team full control to retarget it to a different process node or adjust it to fit alongside the rest of the design. Hard IP ships as a finished physical layout already optimized, verified, and locked to one specific process node — a design team drops it in as a fixed block and gets guaranteed area, timing, and power, but gives up any ability to modify it or move it to a different process without going back to the IP vendor.

Two Forms of the Same Licensed Block how far the IP vendor's work carries into your chip Soft IP RTL source (Verilog) You synthesize + P&R Fits your process, your PDK portable, flexible, timing not guaranteed yet Hard IP Finished GDSII layout Already tied to one process Drop straight into the chip fixed, guaranteed specs, locked to that process node soft IP arrives early in the flow, hard IP arrives already finished

Which form a block ships as is rarely a free choice — it usually follows directly from what the block physically is. A CPU core, a bus fabric, or a simple logic controller is almost always soft IP, because digital logic genuinely benefits from being resynthesized for each target process and integrated design; an SRAM compiler, a PLL, a SerDes PHY, or an ADC is almost always hard IP, because analog and memory circuits are so sensitive to the exact process characteristics that re-layout for every customer would be both wasteful and risky to get right — the category of circuit usually decides the form long before licensing terms do.

Soft IPHard IP
Delivered asRTL source codeFinished physical layout (GDSII)
Process portabilityRetargetable to any compatible processLocked to one specific process node
Integration effortFull synthesis, place-and-route requiredDrop-in block, pre-verified
Performance guaranteeDepends on your own implementationFixed, vendor-guaranteed
Typical examplesCPU cores, bus fabrics, protocol controllersSRAM, PLLs, SerDes PHYs, ADCs/DACs
Source visibilityReadable, often modifiableOpaque, fixed black box

That tradeoff between flexibility and certainty shows up directly in how each type gets licensed and priced. Soft IP licensing usually includes the source code itself, sometimes with a right to modify it, because the customer is expected to carry it through their own implementation flow; hard IP licensing delivers a locked, pre-characterized block with guaranteed timing and power numbers, priced partly for the certainty itself — a customer paying for hard IP is paying to skip the implementation risk entirely, not just to skip writing the RTL.

Read soft IP versus hard IP through a how-far-does-the-vendor's-work-carry lens: soft IP hands over a starting point that still has to be finished inside your own flow, hard IP hands over a finished result that only works inside the exact process it was built for, and the right choice for any given block almost always falls out of whether that block is the kind of circuit that benefits from being redone for every design, or the kind that's safer left untouched.

Take soft IP vs hard IP further

Ask the copilot about this term, or have our engineers assess it against your process.