There is a meaningful difference between making it illegal to build a gun in your garage and making it illegal to email a file. Both Washington State and New York have now stepped across that line, and the second half of the sentence is where the constitutional weather gets interesting.

The public-safety case driving these laws is not imaginary. Untraceable firearms assembled at home from polymer and machined parts leave investigators at what Washington’s attorney general has repeatedly called a “dead end” when a weapon is recovered at a crime scene. Machine-gun conversion devices—the so-called “Glock switches” that turn a pistol into something close to automatic fire—can now be printed in an afternoon. Lawmakers responding to this are not chasing a phantom. The question is whether the tools they have reached for sweep up something the physical-manufacture statutes never touched: the free circulation of information.

What the two states actually did

Washington’s House Bill 2320, signed by Governor Bob Ferguson on March 24, 2026, prohibits using 3D printers and CNC milling machines to manufacture firearms, frames, receivers, and conversion devices. That much is a conventional extension of existing law—Washington already barred untraceable guns; the bill simply names the modern tools. The newer and more contested piece is its regulation of the digital blueprints themselves. State officials describe it as restricting distribution of “gun-making code” while preserving lawful activity by federally licensed manufacturers. The precise statutory reach of that file provision—how broadly “distribution” is defined, what mental state it requires, and where ordinary hobbyist sharing falls—is the part critics in the maker community have flagged most loudly, and it deserves to be read carefully rather than summarized confidently.

New York has gone further and stranger. Governor Kathy Hochul’s package, advanced through 2026, would make it a crime to intentionally sell, distribute, or possess digital instructions to illegally manufacture a firearm or its components without a license. It redefines aspects of the state’s machine-gun law to capture convertible pistols and their “digital printing codes.” And in a genuinely first-in-the-nation move, it reaches the hardware: a signed New York measure directs expert panels to develop standards for “firearm blueprint detection algorithms,” with a mandate—not expected to bite until 2029 or later, pending a feasibility study—that 3D printers sold in the state ship with technology that scans every design, compares it against a library of gun parts, and refuses to print matches. California is weighing a parallel approach.

That last provision is worth sitting with. It is not a rule about guns. It is a rule about what a general-purpose manufacturing device is permitted to do, enforced by an algorithm that inspects the user’s files before they ever become an object.

Why the file is not the gun

The instinct to treat a CAD file as functionally identical to the weapon it describes is understandable, and the law has never fully accepted it. A blueprint is information. It can be read, studied, modified, published in a textbook, embedded in an art project, or used to print a non-functional prop. The moment a state criminalizes the distribution—or worse, the mere possession—of a file, it is regulating the movement of information between people, which is the exact activity the First Amendment was written to protect.

This is the heart of the long-running “code is speech” argument associated with Cody Wilson and Defense Distributed. That saga began over a decade ago when the State Department invoked arms-export controls to stop Defense Distributed from posting its “Liberator” pistol files online, treating the upload as an illegal munitions export. A 2018 settlement briefly cleared the files, then collapsed into renewed litigation as states sued to keep them offline. The unresolved tension underneath it all: source code has long been recognized as carrying expressive content, yet code is also functional—it does things—and the more purely functional it is, the weaker the speech claim becomes.

The most consequential ruling on this to date cut against the file-sharers. In Defense Distributed v. Attorney General of New Jersey (3d Cir. 2026), the Third Circuit upheld New Jersey’s restriction on distributing 3D-printing firearm files, affirming dismissal of both Second and First Amendment challenges. The court declined to assume that computer code is automatically protected speech, distinguished functional code from “inherently expressive” works like a musical score, and held that a challenger must affirmatively show the specific code carries protected expression—the mere “possibility of expressive use” being insufficient. Read narrowly, that is a careful, fact-specific test. Read broadly, it hands states a framework for regulating the distribution of technical information so long as they can characterize it as “purely functional.” Other circuits are not bound by it, and the underlying question feels destined for the Supreme Court.

The privacy problem hiding inside the safety solution

Set the speech question aside and a distinct privacy concern remains, and New York’s detection-algorithm model is where it surfaces most sharply. A printer that scans every submitted design against a government-influenced library of prohibited shapes is, by construction, a surveillance device pointed at your workbench. If that scanning is cloud-based—as such systems often are, for the processing power—then your prototypes, your proprietary designs, your half-finished inventions are being transmitted and inspected by a third party as the price of using a tool you own.

The Electronic Frontier Foundation’s Rory Mir has argued that these “censorship algorithms don’t work, and they wind up capturing and blocking a lot” of legitimate objects—the false-positive problem familiar from every content-matching system ever built. A bracket, a jig, a replica prop, a mechanical part that happens to share geometry with a regulated component: all plausible casualties. And the architecture that makes such filtering possible does not switch off at firearms. Once general-purpose fabrication tools are required to police their users’ files against a centrally defined blocklist, the precedent is portable to any object a future legislature decides is too dangerous to describe.

None of this resolves the underlying dilemma, and honesty requires admitting there isn’t a clean answer. The harm these laws target—untraceable, undetectable, easily-multiplied weapons—is real and rising. But the move from “you may not build this” to “you may not share the file that describes it” to “your machine must refuse files we don’t like” is a move from regulating conduct to regulating information and the tools that process it. Each step is more defensible on safety grounds and more corrosive to the principle that the government regulates what you do, not what you know or what you say. Washington and New York have bet that the public-safety stakes justify the trade. Whether the courts—and the rest of us—agree is a question that, like the files themselves, is now out in the world and impossible to recall.