The 3D Printed Gun Safety Act of 2025 adds a new subsection to 18 U.S.C. §922 that makes it unlawful to intentionally distribute, over the internet or World Wide Web, computer‑aided design (CAD) files or other code that can automatically program a 3‑dimensional printer or similar device to produce a firearm or complete a firearm from an unfinished frame or receiver. The bill targets machine‑readable digital instructions rather than photographs or prose.
This change creates a federal criminal prohibition on a specific category of digital content. That has immediate practical impact on platforms that host user files, makers and hobbyists who exchange designs, researchers and academics who publish printing data, and law enforcement that seeks traceability of firearms.
The statutory language leaves several operative terms undefined and raises constitutional and implementation questions that enforcement agencies and courts would need to resolve.
At a Glance
What It Does
The bill inserts a new clause into 18 U.S.C. §922 making it a crime to intentionally publish or transmit CAD files or other executable code that can automatically program a 3D printer (or similar device) to fabricate a firearm or finish an unfinished frame or receiver. The prohibition specifically covers distribution over the internet and the World Wide Web.
Who It Affects
Online platforms that host or transmit CAD and machine‑executable files, open‑source repositories, CAD authors, hobbyist maker communities, and anyone who posts or downloads 3D‑printable firearm files. Law enforcement and forensic units will also be affected because prosecutions depend on digital evidence and technical analysis.
Why It Matters
The bill shifts a technical problem—machine‑readable schematics that bypass traditional manufacturing and serial‑number regimes—into the criminal code. That creates a new enforcement front that intersects with free‑speech doctrine, platform moderation practices, export controls, and technical classification of what counts as 'code' or 'instructions.' Professionals across compliance, platform policy, and forensic labs will need to reassess risk and procedures.
More articles like this one.
A weekly email with all the latest developments on this topic.
What This Bill Actually Does
The bill is short and focused: Congress proposes to add a single, standalone criminal prohibition to the federal firearms statutes. It names the specific medium—digital CAD files and other code that can automatically program a 3D printer—and the specific outcome—producing a firearm or completing an unfinished frame or receiver.
By targeting the machine‑readable instructions rather than the finished object, the statutory design aims to cut off the online supply chain that makes untraceable, home‑manufactured guns widely accessible.
Operationally, prosecutors would rely on the new §922(aa) to bring cases where an individual or entity intentionally uploads or posts qualifying files on the internet. The statute uses the mens rea term "intentionally," which focuses liability on the actor’s purposeful distribution, but it does not define critical terms such as "computer aided design files," "other code," "automatically program," or what exactly counts as a "similar device." That lack of definition will require development through regulation, guidance, or case law to determine which file formats and delivery methods fall within scope.The bill does not list carve‑outs for academic research, defensive testing, law‑enforcement use, or archival purposes, nor does it enumerate civil remedies or safe‑harbors for platforms that remove content.
Because the prohibition is added to §922—the statutory section that governs many firearms offenses—violations would become federal crimes enforceable by existing criminal procedures and agencies. But the statute’s brevity means questions about evidence standards, digital provenance, intermediary liability, and cross‑border publication are left open.Crucially for compliance teams and platform operators, the language targets files that "can automatically program" a printing device.
That suggests a distinction between executable machine code and human‑readable blueprints; however, technically capable human‑readable files can be converted into machine jobs, raising ambiguity. The practical line between forbidden and permissible content will depend on how courts and regulators interpret "automatically program" and "other code." Enforcement will require technical forensics to show that a file was capable of direct machine execution and that the distributor acted intentionally.
The Five Things You Need to Know
The bill adds a new subsection (aa) to 18 U.S.C. §922 making it unlawful to intentionally distribute, over the internet or World Wide Web, CAD files or other code that can automatically program a 3D printer or similar device to produce a firearm or finish an unfinished frame or receiver.
The statutory prohibition applies to both creating a firearm outright and to completing an unfinished frame or receiver—a common pathway for ‘ghost‑gun’ production that evades serial‑number regimes.
The operative mens rea in the text is "intentionally," so prosecutions must prove purposeful distribution rather than negligent or accidental posting.
The statute targets machine‑executable instructions (CAD files and code) rather than general descriptive or photographic material, but it leaves open whether converted or derivative files, step‑by‑step manuals, or non‑executable blueprints are covered.
The bill does not define key terms (e.g.
"other code," "automatically program," or "similar device") and does not include express exceptions for research, law enforcement, or archival use.
Section-by-Section Breakdown
Every bill we cover gets an analysis of its key sections.
Short title
Gives the act its name, the 3D Printed Gun Safety Act of 2025. This is purely stylistic but signals congressional intent to target public safety risks associated with 3D‑printed firearms.
Findings supporting the prohibition
Enumerates Congress’s factual predicates: advances in 3D printing, the ability to print firearms and parts at low cost, risks of undetectable plastic guns, recent incidents and trace data, and the difficulty of tracing firearms lacking serial numbers. Those findings supply legislative purpose that courts will likely consider when assessing statutory construction and constitutional challenges, and they cite tracing statistics and specific violent events to justify federal action.
Amendment to 18 U.S.C. §922—new distribution offense
Adds subsection (aa) to §922 making it unlawful to intentionally distribute, via internet/WWW, CAD files or other code that can automatically program a 3D printer or similar device to produce a firearm or complete a firearm from an unfinished frame or receiver. The placement inside §922 makes this part of the federal firearms offenses, subject to the broader statutory framework for prosecution and penalties. The provision’s focus on "digital instructions in the form of Computer Aided Design files or other code" narrows target to machine‑readable formats but leaves open ancillary issues—format conversions, links to external files, or the person who merely hosts content versus the person who uploads it.
This bill is one of many.
Codify tracks hundreds of bills on Criminal Justice across all five countries.
Explore Criminal Justice 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
- Federal, state, and local law enforcement—gains a specific criminal tool to prosecute people who disseminate machine‑readable designs for weapons, potentially reducing the online availability of directly printable firearm files and aiding traceability efforts.
- Airports, transportation authorities, and public venues—stand to benefit from reduced risk of firearms engineered to evade metal detectors if the law meaningfully curbs distribution of plastic or low‑metal designs.
- Victims and communities affected by gun violence—may see indirect public‑safety benefits if fewer untraceable firearms are produced and trafficked across jurisdictions.
Who Bears the Cost
- Online platforms and hosting services—face increased compliance and moderation burdens to detect and remove qualifying files and may confront takedown demands or subpoenas without clear safe‑harbors in the text.
- Open‑source makers, hobbyists, and academic researchers—risk criminal exposure when publishing design files or code that a prosecutor deems "capable of automatically programming" a printer, chilling legitimate innovation and research.
- Civil liberties and free‑speech advocates—incur costs defending constitutional challenges and preserving publication rights; national and international repositories may be forced to restrict access to technical materials to avoid liability.
- Forensic labs and prosecutors—must develop technical expertise and procedures to demonstrate a file’s machine‑executable capability and intent to distribute, requiring resources and training.
Key Issues
The Core Tension
The bill pits two legitimate aims: public safety—reducing access to untraceable, potentially undetectable firearms—and protection of speech and research—preserving the publication and exchange of technical files that are often used for lawful purposes; the statutory approach prevents one risk by criminalizing a class of digital content, but it risks overbreadth, vagueness, and chilling of legitimate technical expression without offering clear, narrowly tailored mechanisms to limit collateral suppression.
The bill addresses a discrete threat but does so with compact statutory text that leaves numerous implementation questions unanswered. Key definitional gaps—what counts as "other code," which file formats qualify as CAD, and the meaning of "automatically program"—create uncertainty for both compliance officers and prosecutors.
Platforms may struggle to draw a bright line between banned executable job files and permissible human‑readable schematics, particularly because many work streams convert between those formats. Enforcement will likely depend on technical analysis of file metadata and execution potential, which raises chain‑of‑custody and expertise demands for lawful prosecutions.
Constitutional and doctrinal issues are also unresolved. The statute targets distribution of digital instructions, which sits at the intersection of speech and conduct; courts will need to determine whether a content‑based restriction on machine‑readable code satisfies First Amendment standards or whether it requires a more tailored regulatory approach.
The mens rea requirement "intentionally" narrows scope but leaves open whether hosting platforms, automated mirrors, or search‑engine caches can be liable. Finally, the text does not address cross‑border publication or encryption: files posted on foreign servers or distributed through decentralized technologies may remain accessible, and criminal enforcement against anonymous or offshore distributors will be difficult.
Try it yourself.
Ask a question in plain English, or pick a topic below. Results in seconds.