On October 1 2026, India’s Office of the Controller General of Patents, Designs and Trade Marks (the Controller) published the Draft Guidelines for Registration of Designs Relating to GUI & Icon etc. (the Draft Guidelines). For people who create, launch, and protect digital products, the Draft Guidelines offer a clearer way to understand how graphical user interfaces (GUIs) and icons may be filed, classified, represented, and examined under the Designs Act, 2000 and the Designs Rules, 2001.
This matters wherever the experience of using a screen helps customers recognise and choose a product. Software businesses, digital platforms, consumer-electronics makers, mobility companies, wearable-technology providers, and medical-device companies can use the guidance to make more informed choices about protecting interface designs. It should also help legal, product, and design teams work together earlier, before an interface is disclosed or a product is launched.
The Draft Guidelines do not create a new category of protection or broaden the Designs Act. Instead, they explain how GUI- and icon-related applications should be handled within the existing law. Each business must still assess whether an interface meets the legal requirements, identify the article with which it is associated, and describe the visual features it wants to protect. If the guidance conflicts with the Designs Act or the Designs Rules, the legislation will prevail.
In practical terms, applicants should connect each GUI or icon to an identifiable article, choose a classification based on where the novelty lies, and use precise representations to show what is being claimed. Dynamic interfaces may also qualify, provided the application clearly presents the relevant sequence and meets the statutory requirements.
How the law reached this point
The uncertainty around GUI protection came into sharp focus in UST Global (Singapore) Pte Ltd v The Controller of Patents and Designs and Another, before the Calcutta High Court. The case concerned an application titled “Touch Screen” for a GUI presented as a novel surface ornamentation.
On March 20 2023, the Calcutta High Court confirmed that GUI designs could, in principle, be registered and sent the application back to the Controller for fresh consideration.
The court rejected a blanket rule that GUIs and icons could never qualify as designs. It noted that this view did not reflect amendments to the Designs Rules made in 2019 and 2021. A GUI, the court said, may be a two-dimensional visual design whose novelty can be judged by the eye when a device is switched on. Neither the absence of touch-based interaction nor the fact that an interface appears only after activation should automatically prevent registration.
Even so, the Controller again refused the application on July 6 2023. For applicants and their advisers, that renewed refusal highlighted the gap between the court’s direction and examination practice and the need for clearer, more consistent guidance.
NEC Corporation: greater clarity for applicants
The Calcutta High Court revisited the issue in NEC Corporation v The Controller of Patents and Designs and Another, decided on March 9 2026. The court considered a group of appeals against refusals of GUI-related design applications.
The court held that GUIs are not automatically excluded by Section 2(d) of the Designs Act. Instead, each application must be considered on its own facts and against the statutory requirements. For businesses, this replaces a categorical ‘no’ with a case-by-case assessment.
The court also recognised that applicants had faced an inconsistent landscape: some GUI-related designs had been registered, while others had been refused. It called for clearer guidance so that applicants and examiners could approach these cases with greater certainty. The Draft Guidelines are a response to that need.
What can be protected: static and dynamic interfaces
A GUI is the visual layer through which a person interacts with a device or system on a screen. An icon is a graphical symbol that helps a person recognise a function, command, or application.
The Draft Guidelines recognise both static and dynamic GUIs and icons. This reflects how people now experience digital products across software, consumer electronics, vehicles, wearables, and connected devices.
A static GUI or icon appears in a fixed state. A dynamic GUI or icon changes over time – for example, through a transition, sequence, transformation, animation, or interaction.
That distinction is important because a user’s visual experience often extends beyond a single screen. Recognition of dynamic interfaces, however, does not remove the need to satisfy the legal tests for design registration.
Four questions applicants should ask
Clause 4 of the Draft Guidelines provides a non-exhaustive list of eligibility criteria. In practice, applicants can use them as four questions.
1 What article is the interface connected to?
The GUI or icon must be applied to, or associated with, an identifiable article, such as a mobile phone, tablet, computer monitor, smartwatch, or wearable device.
Accordingly, the Draft Guidelines do not provide for registration of a GUI or icon in the abstract, without identifying the article with which it is associated. This requirement reflects the existing statutory framework and remains an important consideration when preparing an application.
2 Can people see it during normal use?
The GUI must be visually perceptible during normal use. The fact that a GUI or icon becomes visible only when a device is switched on, or that its appearance is not permanent, does not by itself make the design ineligible for registration.
This approach is consistent with the Calcutta High Court’s finding that the Designs Act does not require permanence.
3 Is it generated through an industrial process?
The Draft Guidelines clarify that the generation and display of a GUI or icon by electronic means, including through the execution of software, will suffice for this requirement.
4 Is it new or original?
The GUI or icon must satisfy the applicable requirements of novelty or originality. It must not have been disclosed previously in a manner that defeats registrability, and it must comply with the applicable statutory restrictions, including those concerning scandalous or obscene matter.
Turning the rules into a filing strategy
The Draft Guidelines provide applicants with a more structured path for choosing a classification, naming the application, and preparing the images.
Start by asking where the novelty lies
Under Clause 5.1 of the Draft Guidelines, classification turns on a practical question: is the new visual feature in the GUI, in the article on which it appears, or independently in both?
Novelty resides in the GUI – where novelty lies exclusively in the interface, the application may be classified under Class 14-04 of the Locarno Classification (“Screen displays and icons”), even if the GUI is shown on an article that falls within another class;
Novelty resides primarily in the article – where the novelty lies principally in the article itself, classification may follow the class applicable to that article; or
Independent novelty in both – where the article and the GUI possess independent novelty, separate applications may be filed.
This approach helps applicants choose the right classification and communicate clearly what they want to protect.
Use a title that tells the reader what the design is
The title should identify both the GUI or icon and the article with which it is associated. “Computer Monitor with GUI” works because it gives that context; “GUI”, “Icon”, or “Graphic Symbol” alone does not.
Show clearly what you want to protect
The drawings should make the boundary of the claim easy to understand. The GUI or icon will ordinarily appear in solid lines, while features outside the claim may appear in broken lines. An applicant may instead show the full design in solid lines and identify the GUI or icon in the manner permitted by the applicable practice.
The statement of novelty should then describe, in plain and precise terms, the feature for which protection is sought. The Draft Guidelines give examples such as:
“Novelty resides in the surface ornamentation of the Mobile Phone, as illustrated”;
“Novelty resides in the surface pattern of the Mobile Phone with GUI, as illustrated”; and
“Novelty resides in the shape configuration and surface ornamentation of the Mobile Phone with GUI, as illustrated.”
The lesson is straightforward: the title, drawings, and statement of novelty should tell the same story about what the applicant wants to protect.
What applicants can expect during examination
GUI- and icon-related applications will continue to be examined under the Designs Act and the Designs Rules.
For a GUI application, the Designs Office will search Class 14-04 of the Locarno Classification and the class for the article named in the application. A front view showing the GUI or icon on the screen will usually be enough, although additional views may be included when they help explain the design.
For applicants, this should make the examination process more predictable and help examiners identify relevant earlier designs more consistently.
What businesses should do now
The Draft Guidelines give businesses a clearer route for protecting interface designs that shape how customers experience and recognise digital products in India. Moving from blanket exclusion to case-by-case assessment may strengthen design portfolios and provide another way to respond to imitation. Success will still depend on satisfying the law and clearly identifying the associated article, the visual features claimed, and the basis of novelty.
Legal, product, and design teams should review their interface-development pipelines and GUI and icon portfolios to identify designs connected with upcoming launches. They should then determine whether the novelty lies in the interface, the article, or both, and file before public disclosure. For dynamic interfaces, teams should document the relevant sequence clearly. They should also monitor the final guidelines and update their filing and enforcement strategies if the final text changes.