India's Draft GUI & Icon Design Guidelines: A Critical Analysis

 

I. Introduction: From Judgment to Practice

On 1 October 2026, the Office of the Controller General of Patents, Designs and Trade Marks (CGPDTM) released the draft Guidelines for Registration of Designs relating to Graphical User Interface (GUI) and Icons, inviting stakeholder comments. This draft marks the administrative sequel to the Calcutta High Court’s judgment dated 9 March 2026 in NEC Corporation & Ors. v. Controller of Patents and Designs (2026:CHC‑OS:69), wherein the Court categorically held that there is no per se exclusion of GUIs under Section 2(d) of the Designs Act, 2000.

In my earlier analysis of that judgment, I described it as a watershed for digital design protection in India. The Calcutta High Court, however, also expressly recorded that there was “undoubtedly a lack of clarity in the Designs Office” and called for clarificatory guidance “either by Legislature or by the Controller.” The draft Guidelines now issued by the Controller stand as the administrative answer to that judicial call, providing the much‑needed framework for GUI and icon registration.

The draft Guidelines proceed on two parallel tracks. On the one hand, they must operate within the confines of the existing Designs Act, 2000. On the other, they expressly state that they do not give effect to the DPIIT Concept Note of 23 January 2026, which proposes to decouple design protection from physical articles altogether. The result is a cautious, article‑anchored framework: a genuine step forward on eligibility, yet leaving notable gaps in respect of classification, animated GUIs, and examination standards. These are issues that stakeholders must address before the text is finalised.

This article undertakes a clause‑by‑clause examination of the draft Guidelines, juxtaposes them with leading foreign practices, and concludes with practical filing advice together with concrete suggestions for the ongoing stakeholder consultation.

II. The Legal Framework the Draft Works Within

The draft Guidelines rest upon two statutory definitions reproduced verbatim. Section 2(a) defines "article" as any article of manufacture, including a separately made and sold part. Section 2(d) defines "design" as features of shape, configuration, pattern, ornament or composition of lines or colours applied to an article by an industrial process, which in the finished article appeal to and are judged solely by the eye.

For years, the Designs Office adopted a restrictive reading of these provisions, routinely refusing GUI applications on three recurring grounds:

• No article: the GUI was said to be software, not an article of manufacture.
• No permanence: the GUI appears only when the device is switched on.
• No industrial process: rendering by software was said not to be "application" of a design to an article.

Yet the record revealed inconsistency. The High Court noted that GUIs had in fact been registered, including Siemens’ monitors with GUI (Nos. 274917, 274925, Class 14‑02), Kneevoice’s mobile with GUI (No. 284680, Class 14‑04), and LG’s vehicle navigation device with GUI (No. 276736).

In NEC, the Court rejected all three objections. Permanence is not a statutory requirement, and courts cannot read words into Section 2(d). Electronic rendering on a display‑enabled article qualifies as an “industrial process.” A GUI’s iconography, layout, colour palette, and spacing are aesthetic choices judged by the eye. The Court, however, added two limits that now shape the draft: the GUI must be “properly identified with an article,” and its elements must “not [be] purely function driven.”

Two further strands of law underpin the draft, though not expressly mentioned. First, Section 2(d) excludes trade marks and artistic works under Section 2(c) of the Copyright Act, 1957, and icons often straddle that boundary. Second, the Supreme Court’s 2025 ruling in Cryogas Equipment v. Inox India restated the copyright–design interface under Section 15(2) of the Copyright Act, which is particularly relevant for app icons that also qualify as artistic works.

III. What the Draft Guidelines Say

The draft Guidelines are concise, comprising nine parts in total, with their core resting on four admissibility criteria supplemented by filing formalities.

A. Status and scope

The preamble declares that the Guidelines are “clarificatory and practical,” “directory in nature,” and do not “create, enlarge, restrict or otherwise modify” registrability. They are expressly not founded on the DPIIT Concept Note. Where any inconsistency arises with the Act or Rules, the statute prevails. Notably, the draft discloses that certain illustrations were prepared using AI tools or sourced from the public internet, accompanied by a disclaimer regarding third‑party rights.

B. Definitions (Part 3)

• GUI: a visual interface displayed on a screen through which a user interacts with a device or system.
• Icon: a graphical symbol representing a function, command or application.
• Screen display: the visual output on a display device at a given time.

The draft clarifies that GUIs and icons may be static or dynamic, encompassing transitions, sequences, transformations, animations, or interactions.

C. The four admissibility criteria (Part 4)

Criterion	What the draft requires
4.1 Identification with article	The GUI/icon must be applied to an article such as a phone, tablet, monitor or wearable. A standalone GUI or icon is not registrable.
4.2 Visibility	Must be visually perceptible in normal use. Being visible only when powered on, non-permanent or non-tactile does not by itself defeat registrability.
4.3 Industrial process	Generation and display through electronic means and software execution is sufficient "application by an industrial process".
4.4 Novelty and originality	Must be new or original, not previously disclosed, and not scandalous or obscene under Section 4.

D. Titles and classification (Part 5.1–5.2)

The draft Guidelines make clear that GUIs, icons, and surface patterns per se are not registrable. Where novelty resides solely in the interface, the application may be classified in Locarno Class 14‑04 (“Screen displays and icons”), even if the underlying article falls within another class. Where novelty lies in the article itself, the classification of the article applies. Where both article and interface are novel, separate applications may be filed. Importantly, surface patterns applied to an identifiable article are not to be relegated to the residual Class 32‑01.

The draft also prescribes acceptable titling conventions. Illustrative titles include “Touchscreen with Icons” (Class 14‑04), “Mobile Phone with GUI” (Class 14‑03), “Smart Watch with GUI” (Class 10‑02), and “GUI on Speedometer” (Class 10‑04). Bare titles such as “GUI,” “Icon,” or “Graphic Symbol” are expressly disallowed.

E. Representations, novelty and disclaimers (Part 5.3–5.7)

• The GUI is shown in solid lines; unclaimed parts such as the device frame may be in broken lines, which do not form part of the design.
• Alternatively, the whole may be in solid lines with the GUI "pin-pointed"; if the device is also claimed, all solid lines.
• A front or perspective view ordinarily suffices; all views must be consistent.
• Model novelty statements describe the GUI as "surface ornamentation" or "surface pattern" of, for example, a mobile phone.
• Standard disclaimers apply for broken lines, functionality, mode of construction, letters, numerals and trade marks.

F. Animated GUIs (Part 6)

Dynamic, animated or transitional GUIs are admissible, "provided representation of each frame with GUI is filed as separate designs" — for example as XXXXXX-001 and XXXXXX-002, or as XXXXXX-001 and YYYYYY-001.

G. Examination, objections and term (Parts 7–9)

Examination of GUI and icon applications proceeds under Sections 2, 4, 5, and 35 of the Designs Act, 2000, in the same manner as any other design. In addition, Examiners are directed to search Locarno Class 14‑04 for every application disclosing a GUI, irrespective of the class in which it is filed. The draft enumerates common grounds of objection: improper title or classification, absence of an article, elements that are purely functional, lack of novelty, and unclear or inconsistent representations. Registered GUI designs enjoy the same scope of protection, rights, and term as any other registered design.

IV. Critical Analysis

The draft gets the larger questions right but leaves the operational ones unsettled. Its eligibility rules faithfully track the reasoning in NEC. Yet its classification table, animation provisions, and examination standards risk re‑introducing precisely the inconsistency that the High Court criticised.

A. What the draft gets right

1. It codifies the three key holdings of NEC. Paragraphs 4.2 and 4.3 put beyond doubt that non-permanence, non-tactility and software rendering are no bar. Examiners can no longer refuse on these grounds.
2. It removes the 32-01 trap. Paragraph 5.1.3 stops the practice of parking applied surface designs in the residual class 32-01, and confirms that article-based classification governs.
3. It mandates a cross-class search in 14-04. Requiring examiners to search 14-04 for every GUI application, whatever the filed class, is sound. It prevents the same interface being registered twice in different article classes.
4. It provides for dynamic GUIs. Even with its limits (below), recognising animated and transitional interfaces as admissible subject matter is a meaningful policy choice.
5. It is candid about its sources. The disclosure that some illustrations were AI-generated or taken from the internet is a welcome act of transparency for a public authority.

B. The classification table is internally inconsistent

Paragraph 5.1.2 provides that where novelty resides solely in the interface, the application “may be classified under Class 14‑04,” even if the underlying article falls within another class. Yet the classification table in Paragraph 5.1.4 assigns GUI titles across a mix of interface and article classes without clarifying which novelty scenario each assumes. This lack of alignment risks uncertainty in practice, as applicants and Examiners are left to infer whether the classification is premised on interface novelty, article novelty, or a combination of both.

Title in the draft	Class given	Basis it implies
Touchscreen with Icons	14-04	Interface
Computer monitor with GUI	14-04	Interface
Mobile Phone with GUI	14-03	Article
Screen Display on TV	14-03	Article
Tablet with Icon	14-02	Article
GUI on Speedometer	10-04	Article
Activity trackers with GUI	10-04	Article
Smart Watch with GUI	10-02	Article

 

An applicant whose novelty resides solely in a phone’s interface cannot discern whether to file under Class 14‑03 (as suggested by the table) or Class 14‑04 (as indicated in Paragraph 5.1.2). The use of the word “may” in Paragraph 5.1.2 renders the classification discretionary, inviting divergent practice by different Controllers. Given that classification in India directly affects both the scope of registration and infringement analysis under Section 22 of the Designs Act, this is far from a clerical matter. The final text must prescribe a single, uniform rule and align all illustrative examples accordingly.

C. The article requirement may be stricter than NEC requires

The High Court required that a GUI be “properly identified with an article.” The draft Guidelines translate this requirement into a titling formula and categorically refuse bare titles such as “Icon.” Two problems follow.

• Device-agnostic interfaces. Most modern GUIs run across phones, tablets, laptops, car dashboards and TVs. Tying the title to one device either narrows protection to that device or forces multiple filings, multiplying cost for the same visual creation.
• Projected and immersive interfaces. The draft says nothing on GUIs projected onto surfaces, holograms, heads-up displays, or AR/VR interfaces. Whether a headset or a vehicle windscreen is the "article" is left open.

A generic formulation such as "Display screen or portion thereof with graphical user interface" (the long-standing US model) would satisfy Section 2(a) while avoiding device lock-in. The draft should expressly accept it.

The formula risks collapsing a substantive eligibility test into a formal naming convention, reducing the inquiry to semantics rather than statutory compliance. Further, the outright refusal of bare titles may inadvertently exclude legitimate cases where novelty resides entirely in the interface, thereby re‑introducing the very uncertainty the Court sought to dispel.

D. The frame-by-frame rule undercuts protection for animated GUIs

Requiring each frame of an animated GUI to be filed "as separate designs" is the weakest provision in the draft.

• It protects stills, not motion. The commercially valuable feature of an animated icon or transition is the movement itself. Registering frames separately protects only snapshots. A competitor who copies the transition with slightly different intermediate frames may escape infringement.
• It multiplies cost. A five-stage transition becomes five designs, with five sets of fees, five examinations and five renewals.
• It strains novelty. Individual frames, viewed in isolation, may be commonplace even when the sequence as a whole is new. Examiners will assess each frame alone.
• It is unclear procedurally. The example "XXXXXX-001 and XXXXXX-002" suggests one application number with multiple designs, which the present Act and Rules do not clearly permit for a single class. The final text should explain the filing route.

A more coherent approach, consistent with the present Rules, would be to accept a single design represented by a numbered sequence of views, accompanied by a statement that the views depict successive states of one animated design. This practice is already followed by the EUIPO, the UKIPO, and the USPTO, and it aligns with Rule 14 of the Designs Rules, which governs representations rather than the definition of a design.

E. "Surface ornamentation" is the wrong descriptor

The model novelty statements characterise a GUI as “surface ornamentation” or “surface pattern” of the device. A GUI, however, is more accurately described as a “configuration” or “composition of lines or colours”—precisely the features identified in NEC (layout, proportion, spacing, palette). The “ornamentation” label risks narrowing protection, allowing later arguments that registrability extends only to decorative embellishment rather than to the arrangement of the interface itself. The final text should adopt neutral wording, such as: “Novelty resides in the configuration and composition of lines and colours of the graphical user interface as displayed on the article”.

F. "Purely functional" is undefined

Both Part 7 (“visual appeal and non‑functionality”) and Part 8 (“subject matter being purely functional”) treat functionality as a ground of objection, yet the draft provides no test. In practice, almost every GUI element performs a function. Without guidance, Examiners may refuse a novel button layout simply because buttons are functional.

The draft should instead adopt the standard implicit in NEC: a feature is excluded only if its appearance is dictated solely by its technical function, leaving no scope for designer choice. This mirrors Article 8(1) of the EU Community Design Regulation and reflects the “multiplicity of forms” reasoning familiar in Indian case law.

G. Silence on the copyright and trade mark interface

Icons are frequently both artistic works and, increasingly, registered trade marks. Section 2(d) of the Designs Act excludes both categories from the definition of “design.” Yet the draft Guidelines do not instruct Examiners how to treat an app icon that doubles as a logo, or an icon set originally created as artwork. Nor do they address the interface with Section 15(2) of the Copyright Act, under which copyright in a registrable design ceases once the article is industrially reproduced more than fifty times. For GUIs, the meaning of “reproduced more than fifty times”—whether measured by installations or by devices sold—remains unclear. In light of the Supreme Court’s Cryogas ruling, post‑judgment guidance on this point would be particularly valuable.

H. Prior-art searching is under-specified

The direction to search Locarno Class 14‑04 is necessary but not sufficient. GUI prior art resides largely outside design registers—in app stores, websites, product launch videos, and software documentation. Without a mandate and tools to search such non‑registry sources, novelty examination risks becoming a largely formal exercise, with validity tested only later in cancellation proceedings under Section 19.

I. Status and transition questions

The draft calls itself "directory", but examiners will apply it as binding. It is silent on:

• applications refused or abandoned before NEC and whether they may be refiled or revived;
• pending applications filed with bare titles, and whether amendment of title and class will be allowed under Section 16 without loss of the filing date;
• how the guidelines will be harmonised once the Concept Note amendments, including Hague accession, are enacted.

V. Comparative Perspective

India’s draft Guidelines sit at the conservative end of global practice. They require a named article and split animations into individual frames. By contrast, most major offices now accept device‑neutral titles and permit single applications for animated designs, while several jurisdictions protect GUIs without requiring any associated article at all.

Jurisdiction	Article / device link	Animated GUIs	Notes
India (draft, 2026)	Specific article required in title	Each frame a separate design	Must search Class 14-04 for every GUI application
United States	Since March 2026, display screen need not be drawn if the title identifies the article	Sequence of views in one application	Revised guidance expressly covers projected, holographic, VR and AR interfaces (Banner Witcoff)
European Union	"Product" includes non-physical products and GUIs (reformed Regulation in force from May 2025)	Animation and movement expressly protectable; sequence of views or video file	No article needs to be named
United Kingdom	GUIs protectable as "products"	Successive views of one design	Broken-line and partial designs accepted
Japan	Since 2020, images not recorded on an article (cloud, projected) are protectable	Series of images as one design	Images must relate to operation or display of a function
South Korea	Since 2021, images independent of an article are protectable	Series of images as one design	Mirrors Japanese reform
China	Product with GUI; partial designs since June 2021	Key frames in one application	Large GUI filing volumes

 

Two international instruments add pressure. The NEC judgment itself recorded that 92% of jurisdictions surveyed by WIPO protect GUIs, and that both the Hague Agreement and the Riyadh Design Law Treaty (2024) recognise virtual designs. If India accedes to Hague, as the Concept Note proposes, foreign applicants will arrive with GUI filings drafted for device‑neutral titles and multi‑view animations. Guidelines that insist on per‑frame filings would place India out of step with incoming international registrations.

Comparative entries other than the United States are stated as general practice at the time of writing and should be verified against the relevant office’s current guidance before reliance.

VI. Practical Guidance for Applicants and Practitioners

Until the Guidelines are finalised, applicants should proceed to file GUI designs without delay—conservatively, and in a manner that will satisfy both the draft provisions and the stricter examiners. The NEC judgment already permits registration on a case‑by‑case basis, and every month of delay is a month of lost priority. In practice, applicants should adopt cautious titling, align classifications with both interface and article classes where necessary, and ensure representations follow the numbered‑view format to withstand scrutiny.

1. Always name the article. Use titles like "Mobile Phone with Graphical User Interface" or "Display Screen of a Medical Monitor with GUI". Never file "GUI" or "Icon" alone.
2. Choose the class by where the novelty lies. If only the interface is new, file in 14-04 and say so in the novelty statement. If the device shape is also new, consider a separate article-class application, as paragraph 5.1.2 allows.
3. Cover key devices separately. For an interface used across phone, tablet and car display, file in priority markets with separate titles, or at minimum for the device that matters most commercially.
4. Use broken lines deliberately. Draw the GUI in solid lines and the device frame in broken lines, with a matching disclaimer. This keeps protection focused on the interface and avoids design-around by changing the bezel.
5. Draft novelty statements carefully. Use "configuration and composition of lines and colours of the GUI" in preference to the draft's "surface ornamentation", or combine both, to preserve the broadest reading.
6. Protect animations frame by frame for now. File the most distinctive key frames as separate designs, as the draft requires. Keep a record of the full sequence and its creation dates for copyright and evidence purposes.
7. Add the standard disclaimers. Disclaim text, numerals, trade marks and functional features shown in the GUI, to pre-empt Section 2(d) and functionality objections.
8. Search beyond the register. Before filing, check app stores, product websites and launch videos. GUI prior art is rarely in design registers, and a later Section 19 cancellation will look there.
9. Mind the six-month priority window. For Convention filings, India's six-month priority period under Section 44 applies. Prepare Indian representations in parallel with the home filing so titles and views do not need rework.
10. Review refused or abandoned GUI applications. Assess whether a fresh application, now supported by NEC and the draft, is viable for designs not yet disclosed or still within any applicable window.

VII. Suggested Comments to the Office

Stakeholders responding to the consultation may consider the following ten points, each of which can be implemented within the existing Act and Rules.

#	Draft provision	Suggested change
1	5.1.2 and 5.1.4 (classification)	Adopt one rule: interface-only novelty goes to 14-04, article novelty to the article class. Re-align every example title to that rule.
2	4.1 and 5.2 (article)	Accept generic titles such as "Display screen or portion thereof with GUI" as sufficient identification with an article.
3	Part 6 (animated GUIs)	Allow one design shown by a numbered sequence of views, with a statement that they depict successive states of a single animated design.
4	5.6 (novelty statements)	Add neutral model wording based on "configuration and composition of lines and colours", not only "surface ornamentation".
5	Parts 7 and 8 (functionality)	Define "purely functional" as appearance dictated solely by technical function, leaving no designer choice, following NEC.
6	New provision (icons)	Give examiners guidance on icons that are also trade marks or artistic works, and on Section 15(2) of the Copyright Act for GUIs.
7	4.1 (new technologies)	State the position on projected, holographic, heads-up and AR/VR interfaces, even if only to say they are examined case by case.
8	Part 7 (search)	Mandate searching of non-registry sources (app stores, websites, product videos) and provide examiners with suitable tools.
9	New transitional provision	Permit amendment of title and class in pending applications under Section 16 without loss of filing date.
10	Illustrations	Replace AI-generated or internet-sourced images with Office-created or licensed images, to avoid third-party rights issues in an official publication.

 

Commentators should also urge the Office to publish the final Guidelines with a consolidated set of worked examples. At minimum, these should include: one accepted animated design, one partial design using broken lines, and one refused design on functionality grounds. Such exemplars would provide practitioners with concrete reference points, reduce Controller’s discretion, and promote uniformity across the branches and Controllers.

VIII. Conclusion: A Bridge, Not the Destination

The draft Guidelines mark a significant shift: they translate NEC from a judicial pronouncement into office practice. For the first time, applicants have written assurance that a GUI’s non‑permanence, intangibility, and software rendering will not defeat registration. Yet the draft remains a bridge built within the narrow banks of the Designs Act, 2000. Its insistence on a named article, its frame‑by‑frame rule for animations, and its loose classification table reflect the limits of the present statute as much as the caution of the Office. The fuller solution lies in legislative reform, as proposed in the DPIIT Concept Note—protection for non‑physical designs, Hague accession, and a modern definition of “product.”

Until then, the consultation is the moment to make the bridge sturdy. Clear classification, single‑application animated designs, and a defined functionality test would give Indian designers and global applicants the certainty the Calcutta High Court asked for. With those changes, the final Guidelines could stand as a model of how an administrative office can modernise practice while Parliament completes statutory reform.

Sudhir Kumar is an advocate and patent attorney. The views expressed are personal and do not constitute legal advice.

Sources

• CGPDTM, Draft Guidelines for Registration of Designs relating to GUI & Icon etc. (stakeholder consultation draft, 2026)
• NEC Corporation & Ors. v. Controller of Patents and Designs, 2026:CHC-OS:69 (Calcutta High Court, 9 March 2026) — analysis
• DPIIT Concept Note on amendments to the Designs Act, 23 January 2026 — analysis
• Banner Witcoff, USPTO's Updated Guidelines for GUI and Screen Designs (March 2026)