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 draft Guidelines for Registration of Designs relating to Graphical User Interface (GUI) and Icons, inviting stakeholder comments. The draft follows the Calcutta High Court's judgment dated 9 March 2026 in NEC Corporation & Ors. v. Controller of Patents and Designs (2026:CHC-OS:69), which held categorically that there is no per se exclusion of GUIs under Section 2(d) of the Designs Act, 2000 (see our analysis: Calcutta HC: GUIs Are Registrable Designs).

The High Court 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 are the administrative answer to that judicial call.

The draft proceeds on two parallel tracks. First, it must operate within the confines of the existing Designs Act, 2000. Second, it expressly states that it does 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 on classification, animated GUIs and examination standards — issues stakeholders must address before the text is finalised.

This article examines the draft clause by clause, compares it with leading foreign practice, and closes with practical filing advice and concrete suggestions for the ongoing consultation.

II. The legal framework the draft works within

The draft rests on 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 read these provisions restrictively, 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 and 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 is concise — nine parts in all — with its core resting on four admissibility criteria supplemented by filing formalities.

A. Status and scope

The preamble declares the Guidelines “clarificatory and practical” and “directory in nature,” and states that they do not “create, enlarge, restrict or otherwise modify” registrability. They are expressly not founded on the DPIIT Concept Note, and 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, with a disclaimer on 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.

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

C. The four admissibility criteria (Part 4)

D. Titles and classification (Part 5.1–5.2)

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 in another class. Where novelty lies in the article itself, the article's class applies; where both 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 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 lines are solid.
• 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)

GUI and icon applications are examined under Sections 2, 4, 5 and 35 of the Designs Act, 2000, like any other design. In addition, Examiners must search Class 14-04 for every application disclosing a GUI, whatever the class in which it is filed. Common objections listed include improper title or classification, absence of an article, purely functional elements, lack of novelty, and unclear or inconsistent representations. Registered GUI designs enjoy the same scope, 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 NEC; yet its classification table, animation provisions and examination standards risk re-introducing precisely the inconsistency 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. Searching 14-04 for every GUI application, whatever the filed class, prevents the same interface being registered twice in different article classes.
4. It provides for dynamic GUIs. Even with its limits, recognising animated and transitional interfaces as admissible subject matter is a meaningful policy choice.
5. It is candid about its sources. Disclosing that some illustrations were AI-generated or taken from the internet is welcome transparency from 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 in another class. Yet the table in Paragraph 5.1.4 assigns GUI titles across a mix of interface and article classes without saying which novelty scenario each assumes:

An applicant whose novelty lies solely in a phone's interface cannot tell whether to file in Class 14-03 (as the table suggests) or 14-04 (as Paragraph 5.1.2 indicates). The word “may” makes classification discretionary, inviting divergent practice by different Controllers. Because classification in India directly affects both the scope of registration and infringement analysis under Section 22, this is far from clerical. The final text must prescribe a single, uniform rule and align every illustrative example to it.

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 translates this into a titling formula and categorically refuses 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 is silent on GUIs projected onto surfaces, holograms, heads-up displays and 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, and the draft should expressly accept it. As drafted, the formula risks collapsing a substantive eligibility test into a naming convention, and the outright refusal of bare titles may exclude legitimate cases where novelty lies entirely in the interface — 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. A competitor who copies the transition with slightly different intermediate frames may escape infringement.
• It multiplies cost. A five-stage transition becomes five designs — five sets of fees, five examinations, five renewals.
• It strains novelty. Individual frames viewed in isolation may be commonplace even where the sequence as a whole is new, yet examiners will assess each frame alone.
• It is procedurally unclear. 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.

A more coherent approach, consistent with the present Rules, is to accept a single design represented by a numbered sequence of views, with a statement that the views depict successive states of one animated design. This is already the practice of the EUIPO, UKIPO and USPTO, and it sits comfortably 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 describe a GUI as “surface ornamentation” or “surface pattern” of the device. A GUI is more accurately a “configuration” or “composition of lines or colours” — precisely the features identified in NEC (layout, proportion, spacing, palette). The “ornamentation” label risks later arguments that protection extends only to decorative embellishment rather than to the arrangement of the interface itself. Neutral wording is preferable, 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

Part 7 (“visual appeal and non-functionality”) and Part 8 (“subject matter being purely functional”) both treat functionality as a ground of objection, but the draft offers no test. Almost every GUI element performs a function; without guidance, Examiners may refuse a novel button layout simply because buttons are functional. The draft should 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 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 — and Section 2(d) excludes both from the definition of “design.” Yet the draft does not tell Examiners how to treat an app icon that doubles as a logo, or an icon set originally created as artwork. Nor does it address 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, whether “more than fifty times” is measured by installations or by devices sold remains unclear. In light of Cryogas, guidance here would be particularly valuable.

H. Prior-art searching is under-specified

The direction to search Class 14-04 is necessary but not sufficient. GUI prior art lives largely outside design registers — in app stores, websites, product-launch videos and software documentation. Without a mandate and tools to search these sources, novelty examination risks becoming formal, 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 title and class may be amended under Section 16 without loss of filing date;
• how the Guidelines will be harmonised once the Concept Note amendments, including Hague accession, are enacted.

V. Comparative perspective

India's draft sits at the conservative end of global practice. It requires a named article and splits animations into individual frames, whereas most major offices now accept device-neutral titles and single applications for animated designs — and several protect GUIs without any associated article at all.

Two international instruments add pressure. NEC itself recorded that 92% of jurisdictions surveyed by WIPO protect GUIs, and 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; per-frame filing would put India out of step with incoming international registrations.

Comparative entries other than the United States reflect general practice at the time of writing and should be verified against each office's current guidance before reliance.

VI. Practical guidance for applicants and practitioners

Until the Guidelines are finalised, applicants should file GUI designs without delay — conservatively, and in a form that satisfies both the draft and the strictest examiner. NEC already permits registration case by case, and every month of delay is a month of lost priority.

1. Always name the article. Use titles such as “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 separate titles in priority markets — 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, so protection stays on the interface and cannot be designed around by changing the bezel.
5. Draft novelty statements carefully. Prefer “configuration and composition of lines and colours of the GUI” to “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, and keep a record of the full sequence and creation dates for copyright and evidence.
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. Check app stores, product websites and launch videos before filing — a later Section 19 cancellation will look there.
9. Mind the six-month priority window. For Convention filings, prepare Indian representations in parallel with the home filing so titles and views need no rework within the Section 44 period.
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.

Commentators should also urge the Office to publish the final Guidelines with a consolidated set of worked examples — at minimum one accepted animated design, one partial design using broken lines, and one design refused on functionality grounds. Such exemplars would give practitioners concrete reference points, narrow Controllers' discretion and promote uniformity across branches.

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 — and could make the final Guidelines a model of how an administrative office modernises practice while Parliament completes statutory reform.

Sources

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