AB 2047 (California Firearm Printing Prevention Act) directs the State to develop performance standards and a certification program for firearm-blueprint detection algorithms and software controls, and it requires manufacturers to equip any three-dimensional printer offered in California with certified blocking technology and to file a make-and-model attestation. The bill sets timelines for guidance, certification, public lists of certified algorithms/processes and attested printer models, and an operative sales prohibition for noncompliant printers.
The statute creates enforceable duties across multiple links in the 3D-printing supply chain: algorithm and software vendors must satisfy state testing and disclosure requirements to be certified; printer manufacturers must integrate certified solutions and either obtain a voluntary verification or file an attestation; retailers and distributors must consult the state list before selling. The act also includes civil causes of action, a $25,000 per-violation penalty for government enforcement, and carve-outs for licensed firearms manufacturers, government purchasers, and certain industrial-only printers — making it a model for regulating embedded safety tech in consumer hardware.
At a Glance
What It Does
The bill requires the Department of Justice (or another designated state agency) to publish performance standards and certify both firearm-blueprint detection algorithms and software control processes, then requires manufacturers to equip printers sold in California with those certified components and submit a make-and-model attestation. The department maintains public lists of certified algorithms and attested or verified printer models and can revoke certifications.
Who It Affects
Consumer and commercial 3D-printer manufacturers (make/model level), slicer and firmware vendors, retailers and distributors selling printers in California, and software providers that generate geometric code for printers. The department and any labs or contractors that perform testing will also bear operational responsibilities.
Why It Matters
This is one of the first state laws to mandate integrated algorithmic blocking technology in a mass-market hardware product to address an illicit-manufacturing risk. It forces design changes in firmware and preprint software, creates certification markets for detection tools, and raises practical questions about detection accuracy, update cadence, interoperability, and impacts on open-source ecosystems.
More articles like this one.
A weekly email with all the latest developments on this topic.
What This Bill Actually Does
AB 2047 creates the California Firearm Printing Prevention Act and builds a layered regulatory program. The statute starts by defining key terms — what counts as a firearm, firearm precursor parts, a firearm blueprint detection algorithm, firearm blocking technology, firmware design, and integrated pre-print software design — to make clear the law targets the files and technical paths that turn digital blueprints into printed parts.
The definitions guide how the rest of the law treats software embedded in printers versus external slicers and how ‘‘illegal firearm parts’’ are identified.
The department (the DOJ) must first research existing firearm blueprint files and detection techniques and may assemble a secured library of disallowed blueprints to support algorithm designers. It must publish performance standards by mid-2027 for detection algorithms and software control processes; those standards require high accuracy in identifying files that would produce firearms or illegal parts, the ability to detect commonly shared and modified blueprint variants, and a mandate to implement regular updates.
The department can compel previously certified vendors to adopt superior detection techniques if a materially better method emerges, and it will maintain public registries of certified algorithms and software control processes.On the controls side, the statute sets out acceptable design forms for preventing prints without prior algorithmic evaluation: firmware-level integration, preprint software that is the printer’s exclusive input source, and other designs (e.g., handshake authentication) if shown to be as effective and as resistant to skilled evasion. The written guidance must explain how vendors demonstrate that a design reliably routes potential print jobs to detection algorithms and resists circumvention.Manufacturers face direct obligations.
By mid-2028 any business that intends to place a printer model on the California market must submit a self-attestation confirming the model is equipped with certified detection and software control components and that testing was performed to department standards. Manufacturers can apply for a voluntary verification in which the department inspects hardware and issues a written notice of compliance; that notice provides a limited shield from civil liability.
The department will publish make-and-model lists (complete attestations, incomplete attestations, verified models, and pending verifications) and updates them quarterly. The substantive prohibition on selling or transferring a noncompliant printer becomes operative March 1, 2029, and the statute creates a private right of action, an enforcement path for the Attorney General and local governments with penalties up to $25,000 per violation, and recovery of attorney’s fees.
The Five Things You Need to Know
The department must publish performance guidance for detection algorithms and software controls by July 1, 2027, and begin accepting certification applications for both on January 1, 2028.
Manufacturers must submit a make-and-model self-attestation (confirming installation of certified detection and controls and testing) by July 1, 2028; they may seek voluntary verification by the department, which issues a written notice of compliance.
Selling or transferring a three-dimensional printer in California that is not equipped with certified firearm blocking technology and listed by the department becomes unlawful on March 1, 2029, and violations expose sellers to private suits and civil penalties (up to $25,000 per violation by government prosecutors).
The department will require detection algorithms to use and regularly update an inventory of disallowed blueprint files (including common public variants), allow testing access to vendor technology, and may revoke certification for failure to update or match state-of-the-art techniques.
Exemptions cover printers made exclusively for licensed firearms manufacturers, state or federal law enforcement, or certain industrial buyers (aerospace, biomedical, automotive, engineering contractors) that are not sold on the consumer retail market.
Section-by-Section Breakdown
Every bill we cover gets an analysis of its key sections.
Definitions that frame what the law targets
This section sets the technical and legal vocabulary the program uses: ‘‘firearm blocking technology’’ covers hardware, firmware, or other integrated measures; ‘‘firearm blueprint detection algorithm’’ covers services that evaluate STL and other CAD files; ‘‘firmware design’’ and ‘‘integrated preprint software design’’ describe two specific integration paths for enforcement; and ‘‘illegal firearm parts’’ is defined to include precursor parts and conversion devices. For implementers, these definitions delimit whether a given piece of firmware, slicer, or accessory falls inside the statute and whether an STL or G-code route is subject to detection and blocking requirements.
Algorithm research, performance standards, and certification
The department must investigate existing firearm blueprints and existing detection tools, may create a secured blueprint library to help train and test algorithms, and must publish performance standards for detection algorithms by July 1, 2027. Certified algorithms must accurately evaluate STL and other geometry files, detect files that would produce firearms or illegal parts, flag disallowed files, use a catalog of commonly shared disallowed blueprints (and variants), and implement regular updates. Applicants must disclose the file inventory used to design the algorithm and provide testing access and technical schematics to the department. The department will publish a publicly accessible list of certified algorithms and can revoke certification for inadequate updates or performance; revocation triggers manufacturer notification and a minimum three-month cure window.
Software controls performance standards and certification
This section requires the department to issue standards for systems that prevent a print unless the file has been evaluated by a certified detection algorithm. The guidance identifies acceptable designs — firmware integration, single-preprint-software models, or other forms (for example, handshake authentication) if they match the effectiveness and resistance-to-evasion of the named designs — and requires testable demonstrations of those properties. Certification follows a similar application-and-testing routine as for algorithms, the department lists certified processes online, and the agency can revoke certification if a process later fails to meet standards, again triggering notification and a three-month manufacturer remedy period.
Manufacturer guidance on equipping printers
The department must publish guidance for manufacturers by March 1, 2028 explaining how to equip printers with certified detection algorithms and software controls and how to test their integrated functionality to meet reliability thresholds. The guidance provides the practical checklist manufacturers will use to design compliance into product development and quality-assurance processes: which certified components to reference, how to demonstrate routing of print jobs through the detection layer, and how to document testing results for attestations or voluntary verification applications.
Attestation, voluntary verification, and public make-and-model lists
Manufacturers must submit a self-attestation for each make and model they intend to sell in California, confirming installation of certified components and testing, starting July 1, 2028. The department offers an optional verification program where it inspects sample hardware and issues a written notice of compliance — a verification that removes exposure to civil suits under Section 3273.637 for that model unless the underlying certification is later revoked. The department posts quarterly-updated lists identifying models with complete attestations, incomplete attestations, verified models, and models with pending applications; retailers are expected to consult the lists before selling in California.
Sale prohibition, enforcement, and civil remedies
The statute makes it unlawful to sell or transfer a printer in California that is not equipped with firearm blocking technology and not listed by the department as attested, verified, or pending verification, with limited exemptions. It creates a private right of action for harmed persons and authorizes actions by the Attorney General, county counsel, or city attorney seeking penalties up to $25,000 per violation and injunctive relief. Filing false attestations is separately actionable and may trigger criminal perjury exposure. Remedies are cumulative and manufacturers, distributors, and retailers have specified affirmative defenses tied to reliance on the department’s published lists or a written notice of verification.
Regulatory authority and implementation tools
The department may adopt regulations and create forms and publications needed to implement the title. That delegation gives the agency typical rulemaking tools to refine testing procedures, submission templates, confidentiality protections for sensitive test data, and operational details for managing the secured library and public lists — which will be key to the program's practicability and industry uptake.
This bill is one of many.
Codify tracks hundreds of bills on Technology across all five countries.
Explore Technology in Codify Search →Who Benefits and Who Bears the Cost
Every bill creates winners and losers. Here's who stands to gain and who bears the cost.
Who Benefits
- Law enforcement and public-safety advocates — by reducing an accessible route for illicit production of firearms and providing a centralized, certified detection capability to block common blueprint-derived prints.
- Compliant manufacturers and verified brands — producers that integrate certified blocking tech early gain a market advantage and a safe-harbor from certain civil suits when they obtain departmental verification.
- Vendors of certified detection algorithms and software controls — the law creates a new certification market and recurring demand for updated threat inventories and maintenance contracts.
- Retailers and distributors who use the department’s lists — the published make-and-model list gives them an affirmative defense if they rely on it before selling, reducing their downstream legal risk.
Who Bears the Cost
- 3D-printer manufacturers — required to integrate certified firmware or exclusive preprint software, perform testing to departmental standards, and file attestations or pursue voluntary verification, all of which raise engineering, compliance, and administrative costs.
- Open-source firmware and slicer ecosystems and hobbyist communities — the law’s emphasis on exclusive preprint software or locked firmware likely restricts alternative slicers and community-driven firmware modifications, reducing interoperability and increasing barriers for DIY users.
- The department (DOJ) and its contractors — tasked with building secure blueprint libraries, running evaluations, certifying vendors, conducting verifications and inspections, and maintaining public lists, creating ongoing operational costs.
- Small manufacturers, importers, and specialty resellers — these actors may face disproportionate compliance burdens and legal exposure if they rely on supply chains with mixed compliance or cannot afford voluntary verification testing.
Key Issues
The Core Tension
The central dilemma is whether to prioritize near-term prevention of weaponized prints by hardening consumer hardware through certified, often closed, technical controls — at the cost of constraining interoperability, open-source innovation, and some legitimate industrial uses — or to preserve an open technology ecosystem that makes robust, enforceable prevention harder to achieve. The bill opts for mandated technical gating, but implementing that choice without overblocking lawful activity or creating perverse incentives for adversarial redesign is the difficult trade-off policymakers and implementers will have to manage.
AB 2047 tackles a technical arms race by tying legal compliance to algorithmic performance and system design, but that approach raises practical implementation questions. Detection algorithms will necessarily trade off false positives and false negatives; the bill explicitly declines to demand perfection, yet enforcement will have to accommodate mistaken rejections of legitimate industrial files and failures to catch adversarially altered blueprints.
Determining acceptable thresholds for ‘‘a high degree of accuracy’’ and operationalizing regular updates will require technical calibration in rulemaking and test procedures that are not detailed in the statute.
The statute also reshapes product design incentives. Mandating exclusive preprint software or firmware-level controls pressures manufacturers to ship closed ecosystems or controlled input pathways, which conflicts with longstanding open-source and hobbyist practices.
The department’s secured library of disallowed blueprints is intended to improve detection, but it creates its own vulnerabilities: how the state secures and governs access to that library, how it balances transparency for testing with risk of misuse, and how it prevents leakage that could accelerate illicit design innovation are unresolved operational risks. Finally, revocation mechanics (notification plus a minimum three-month cure window) set hard timelines, but do not fully resolve transitional questions like how to treat models already in the retail pipeline or imported units, or how to handle conflicting certifications across jurisdictions.
Try it yourself.
Ask a question in plain English, or pick a topic below. Results in seconds.