Home/Glossary/TSMC Mask Costs
Semiconductor knowledge

TSMC Mask Costs

The project-specific cost of photomasks used for fabrication in a selected TSMC process. Pricing varies with the technology, mask requirements, prototype arrangement and design changes.

← All glossary termsTechnical guide · 5 min read
In this article

The project-specific cost of photomasks used for fabrication in a selected TSMC process. Pricing varies with the technology, mask requirements, prototype arrangement and design changes.

ASIC cost planning areas
Planning categories only. This illustration contains no supplier prices or fabricated cost proportions.

What a mask estimate represents

Photomasks carry the patterns used during wafer fabrication. In an ASIC budget, mask-related costs are part of the non-recurring investment required to introduce or change a design. The estimate depends on the selected process, required mask layers, manufacturing options and commercial arrangement. There is no reliable universal public price for a TSMC mask set that applies to every customer and technology. Treat unsourced online numbers as incomplete context rather than a procurement quotation, especially when they omit the process variant or date.

Why revisions matter

A design change after release can require different amounts of mask work depending on which layers and structures change. A limited engineering change and a complete design revision are not automatically priced the same way. Engineering teams should not assume that a change is inexpensive because it appears small in the RTL. Its physical impact must be reviewed. Keep the layout revision, proposed change, verification impact and manufacturing implications together when requesting an estimate, and confirm which existing work can actually be reused.

Shared runs and dedicated production

A multi-project wafer arrangement can share fabrication resources among several designs, subject to the provider's process, area and schedule rules. It can be useful for prototypes, but its economics and delivery conditions differ from dedicated production. Check what the quoted package includes: design area, masks, wafer processing, delivered die, packaging and test may be handled differently. A low initial prototype charge does not establish the eventual production cost. Evaluate the path from the first experiment to a repeatable product supply arrangement.

Build a complete cost question

When asking about masks, include the technology, design maturity, expected tape-out timing, production objective and possible revision plan. Then compare mask expenditure with design effort, licensed IP, packaging development and test preparation. A project can save on one item while increasing total risk elsewhere. Use scenario ranges for expected volume and possible respins, and identify the assumptions that dominate the decision. This produces a more useful business case than asking for a mask price without the surrounding product context.

Questions about mask budgets

Can a mask cost be inferred from the node name alone?

No. The node label leaves out process options, mask requirements, commercial scope and other project-specific factors. Obtain a current quotation for the actual manufacturing plan.

Should mask costs be included in unit cost?

They are normally tracked as non-recurring expenditure, but a business case can allocate that investment across an expected volume. Keep the allocation visible so it is not confused with the recurring manufacturing price.

Establish a common comparison boundary

List every activity required to reach the intended product milestone. Depending on scope, this can include architecture, source design, verification, implementation, IP, masks, fabrication, packaging, test and validation. Identify customer-supplied work and external dependencies. Two quotations are not directly comparable when one excludes essential activities that the other includes. Separate firm supplier information from preliminary engineering estimates and state the date or context of commercial inputs where available. A transparent boundary makes the budget useful for decisions instead of merely producing a single attractive number.

Model the drivers and uncertainty

Production volume, die area, yield assumptions, package choice and test effort can influence recurring cost. Development complexity, IP and the possibility of revision affect non-recurring investment. Use scenario ranges where the evidence is uncertain. Identify which variables have the greatest effect on the conclusion and obtain better information about those first. Avoid publishing invented prices or a universal break-even volume. The model should help a project team understand its own decision, including what would change if demand, architecture or the manufacturing route differs from the initial expectation.

Stage commitments around evidence

Link spending decisions to concrete learning. A feasibility study can test an architectural assumption, a prototype can support integration work, and characterization can establish important silicon behavior. Define what each stage must demonstrate before the next commitment. This does not eliminate risk, but it makes the remaining uncertainty visible. Preserve the assumptions behind an approved budget so later changes can be discussed coherently. A schedule or cost revision is easier to evaluate when the team can identify the requirement, supplier condition or technical finding that caused it.

Include lifecycle and opportunity cost

Compare the custom chip with credible alternatives over the expected product life. Consider software, board changes, inventory, support and the flexibility lost or gained. A low initial cost may be less attractive if it leaves the product dependent on an unsuitable component or makes a likely revision difficult. Conversely, a custom design can be unnecessary when an available solution meets the real requirements. The final recommendation should connect expenditure to product value and acknowledge the conditions under which another approach would be preferable, rather than treating custom silicon as a goal independent of the business need.

Primary reference for further reading

A practical cross-discipline review

Before committing the next stage, bring the design, verification and product-engineering owners together around the same revision. Confirm the assumptions that pass between them: operating modes, interfaces, test access and the evidence expected at release. List unresolved issues with a responsible owner and a concrete way to close them. An open question is easier to manage when its consequence is understood than when it is hidden inside a general progress estimate. Preserve the decision record so a later change can be evaluated against the original reasoning. This review is useful even for a narrow specialist task, because the surrounding product still determines whether the delivered result is usable.

Include the receiving team's acceptance question in the review: what must be demonstrated before this result can be used safely in the next engineering stage? Agree how that demonstration will be recorded and how a subsequent change triggers a focused reassessment of the affected evidence.

Explore the related Avnet offering or discuss your project requirements.

Let's talk about your next project.

Explore design, technology enablement and manufacturing with Avnet ASIC Solutions.

Contact our team →