USPTO Lets GUI Designs Move Beyond the Physical Screen
The USPTO has materially changed how design patent applications for graphical user interfaces are expected to establish their connection to an article of manufacture. On March 13, 2026, the Office published supplemental examination guidance for computer-generated electronic images and icons, effective immediately for pending and future matters. By mid-August, as examiner training and practitioner implementation spread, the change was increasingly being treated in practice as part of routine examination. The timeline matters: March 13 is the formal effective date of the guidance, while August 18 is better understood as a practitioner-reported execution milestone rather than a new legal commencement date.
The practical shift is straightforward but consequential. An applicant no longer has to draw a conventional display panel, handset outline, or monitor border in solid or broken lines merely to anchor a GUI to a physical screen. If the title and claim properly identify the relevant article—such as a computer, computer system, or computer display device—a projected interface, holographic image, or interface used in virtual or augmented reality can satisfy the article-of-manufacture requirement under 35 U.S.C. §171 even when the visual design is spatially separated from the hardware that generates it. But “screenless” does not mean “article-free”: an isolated or transient digital image that is not legally tied to a computer or computer system can still fall outside design-patent eligibility.
The rule change is about how the article relationship is shown
For years, U.S. GUI design practice treated the physical display as a powerful visual anchor. Even when the applicant wanted protection only for the interface itself, drawings often included a broken-line phone, monitor, panel, or display boundary to make clear that the claimed design was not simply a disembodied image. The 2026 guidance separates two ideas that had often been handled together: the design still needs a legally sufficient relationship to an article, but that relationship no longer has to be expressed through a visible screen outline in every drawing.
Examiners are directed to read the disclosure as a whole, with particular attention to the title and claim. If those elements correctly identify the interface as being for a computer, computer system, or computer display device, the drawings may focus on the visual subject matter for which protection is sought. Applicants may still use broken-line display environments, but the screen frame is no longer the only way to establish compliance with §171.
This is more than a drafting convenience. In design patents, solid lines and broken lines shape what is claimed and what is merely environmental. A device frame added only to satisfy an article requirement can create unnecessary anxiety about whether the protected visual scope has been tethered to a particular terminal or display configuration. The new approach gives applicants more room to keep the drawings centered on the interface itself. The trade-off is that titles, claims, and descriptions must now do more work. A clean drawing package paired with vague textual identification can still create an eligibility problem.
“For a computer” is no longer throwaway wording
One of the most important practical lessons is that article-identifying language in the title and claim should not be treated as formality. The guidance accepts formulations that connect a projected, virtual-reality, augmented-reality, or other computer-generated interface to a computer or computer system. The point is not a magic phrase. The point is to show that the applicant is claiming an ornamental visual design used with an identified article, rather than attempting to monopolize an abstract digital image as such.
That distinction changes drafting priorities. A claim framed only as an “icon” or “interface,” with no meaningful link back to a computer environment elsewhere in the disclosure, may still be vulnerable. By contrast, once the article relationship is properly established, the fact that the image is not physically fixed to a conventional display surface is no longer decisive.
For cross-border filing teams, this suggests a more disciplined sequence. Start by defining the protected subject matter: is it a GUI, a projected icon, a holographic interface, an AR overlay, or a VR dashboard? Then identify the relevant computer, display, or system relationship in the title, claim, and description. Only after that should the team decide which environmental elements belong in the drawings. The text and the figures should tell the same legal story.
Holograms, VR and AR are eligible examples—not a shortcut to protecting functionality
The most visible part of the guidance is its recognition that projected images, holographic images, and interfaces presented in virtual or augmented environments may qualify for design patent protection. The critical premise is that the visual design remains for a computer, computer display, or computer system and is properly disclosed and claimed, even if the appearance is spatially separated from the generating hardware.
That matters for head-up displays, smart glasses, spatial computing, immersive training systems, industrial AR, and other products whose visual experience is deliberately detached from a conventional screen. Previously, teams developing those products often faced a mismatch: the commercial value lay in a floating or projected interface, yet the U.S. design filing strategy still encouraged them to place that interface back inside a drawn display boundary. The supplemental guidance reduces that mismatch at the §171 stage.
The boundary should not be overstated. The USPTO has not converted software logic, business processes, or abstract interaction rules into design patents. Section 171 still requires an ornamental design, and applications remain subject to other requirements, including novelty, nonobviousness, and adequate disclosure under 35 U.S.C. §§102, 103 and 112. A sequence such as “a menu appears when the user reaches toward the interface” is not protected merely because the sequence is illustrated. What matters is the claimed visual appearance, properly and sufficiently disclosed.
Filing strategy should shift from device-frame dependence to interface-state architecture
The most useful immediate adjustment is to change how teams prepare GUI filings before drawings are commissioned. The first question should no longer be whether to show a phone or monitor border. It should be which visual states carry actual commercial value. A static home screen, an expanded control panel, a projected keyboard, a floating spatial icon, a VR instrument cluster, and an AR guidance layer may all belong to one user experience but may not belong in one indistinct design claim.
View completeness also deserves more attention. Removing a mandatory screen boundary does not relax the disclosure requirements under 37 CFR 1.152 or §112. For projected and spatial interfaces, perspective, curvature, surface variation, and state changes may matter more than they did in traditional flat-screen filings. If the drawings show only one planar or frontal appearance, the resulting protection should not be assumed to extend automatically to materially different presentations on curved or irregular surfaces.
Timing is the final operational issue. GUI assets often evolve faster than hardware, and public disclosure may occur through developer conferences, product videos, beta releases, or live demos before the device itself is finalized. U.S. design applications remain exposed to novelty and obviousness issues. Legal teams that wait for hardware lock may lose useful filing opportunities. A better workflow is to track interface versions, first-publication dates, key visual states, and intended claim sets as part of the product design process.
The core change is therefore narrower—and more useful—than saying the screen no longer matters. The article relationship still matters, but it can now be established through the title, claim, and complete disclosure rather than being drawn into every GUI figure. For holographic, projected, VR and AR products, that brings U.S. design patent practice closer to how digital interfaces actually appear. For applicants, it also raises the value of coordinated claim drafting and deliberate visual-scope planning.
