Home > Resources > Trademark FAQs > Mobile App Icon Trademark FAQs

Mobile App Icon Trademark FAQs

This page explains how mobile app icons can function as trademarks in India, including classification, clearance, filing format, use claims, ownership, third-party artwork, copycat-app enforcement, overlapping copyright and design rights, renewal and international strategy.

Important scope note. App-icon protection depends on the exact sign, the goods and services, prior rights, ownership and use evidence. A filing or enforcement decision should be based on the current Trade Marks Act, Rules, Registry records and the actual artwork rather than generic app-branding assumptions.

A. App Icon as a Trademark: Nature, Scope and Separate Rights

Yes. An app icon can function as a trademark if it is capable of distinguishing the goods or services of one undertaking from those of others. In practice, the icon is generally filed as a device or figurative mark. Registration protects the source-identifying sign as filed; it does not create ownership over the general idea of having an app icon.

No. Trademark law protects the sign as a badge of commercial origin, while copyright can protect qualifying original artistic expression in the artwork. The two rights can overlap, but trademark registration does not prove copyright ownership and copyright ownership does not automatically establish trademark registrability.

Not necessarily. A device mark containing words is protected as the composite mark filed, subject to the Act and any non-distinctive elements. A separate word-mark application is usually considered where the app name itself is commercially important and protection is required independently of the graphic treatment.

No. A word mark and a device icon are different signs. Registration of the name can be valuable against confusing word use, but a materially different copycat icon may require reliance on a separate device registration, passing off, copyright or other rights.

Ordinarily, a common app-icon container or basic geometric shape will have limited inherent distinctiveness by itself. Registrability and scope depend on the overall device, including its distinctive graphic elements, arrangement, stylisation, colours where claimed, and any words or symbols. Functional or commonplace design conventions should not be treated as exclusive merely because they appear within a registered composite mark.

Yes. Section 18 permits an application by a person claiming to be proprietor of a trademark used or proposed to be used. If genuine commercial launch has not yet occurred, a proposed-to-be-used basis can be more accurate than inventing or overstating an earlier use date.

No. Store approval is governed by platform rules and does not decide trademark ownership, registrability or infringement. Store records can, however, become useful evidence of launch, presentation, account control and public use.

Potentially yes. Charging a download price is not the sole test for trademark use. A free app can still form part of a commercial or business offering and use the icon to identify source. The factual use should nevertheless be genuine, public and connected with the relevant goods or services rather than merely private, experimental or dormant.

Yes, but the trademark specification must reflect the goods and services actually provided or genuinely proposed. The icon may identify the downloadable application in Class 9 while also identifying separate services delivered through or around the app in one or more service classes. Registration should not be expanded into unrelated classes merely because the same icon appears there.

No. Registration of one icon protects the registered sign within the statutory scope. UI screens, animations, code, text, layouts, product names and other brand elements may involve separate trademark, copyright, design, contract or confidentiality issues.

B. Nice Classification, Search and Registrability

The Trade Marks Rules require classification according to the current edition of the Nice Classification published by WIPO. In 2026, the current Nice Classification is the 13th Edition, Version 2026, effective from 1 January 2026. The applicant should still use current Registry-accepted terminology when drafting the goods or services specification.

Class 9 is ordinarily relevant where the applicant provides downloadable computer software or a downloadable mobile application. The wording should describe the actual software rather than rely on an unnecessarily broad class heading.

Class 42 can be relevant for software as a service, platform as a service, providing online non-downloadable software, software development, hosting and other technology services. It is not automatically required merely because an app exists. The applicant should distinguish a downloadable software product from the cloud or technology services actually supplied.

That depends on the underlying service. Examples can include Class 35 for specified business or marketplace services, Class 36 for financial services, Class 38 for telecommunications, Class 41 for education or entertainment, Class 43 for certain accommodation or food-related services, Class 44 for medical or wellness services, and Class 45 for specified legal, security or social services. The classification follows the service, not the fact that it is accessed through an app.

No. There is no mandatory three-class formula. Filing strategy should follow the actual business model, genuine expansion plan and budget. Overbroad specifications can increase cost and future non-use exposure without adding useful protection.

A useful search combines word searches for any letters or words in the icon, phonetic searches where wording is relevant, device or figurative searches using Vienna coding, visual review of earlier marks in the relevant and allied classes, and broader marketplace, app-store, company-name, domain and web searches for unregistered use.

Vienna Classification is an international system for classifying figurative elements of marks. The Indian Trade Marks Registry uses Vienna codification for device marks as a search and examination aid. A Vienna code does not determine registrability; it helps locate earlier marks containing similar visual elements.

No. Search results reduce uncertainty but do not bind the Registrar and do not eliminate unregistered prior rights, later-filed priority claims, well-known marks, fresh Registry records or examiner judgment under Sections 9 and 11. A search is an assessment tool, not a registration guarantee.

Section 9 absolute-ground objections can arise where the icon lacks distinctive character or consists substantially of descriptive, customary or otherwise non-distinctive visual matter. Common pictograms such as an ordinary camera, shopping cart, location pin, gear or medical symbol can be difficult to monopolise alone for closely related goods or services unless the overall stylisation creates sufficient distinctiveness or acquired distinctiveness can properly be shown.

Potentially. The Section 9 framework recognises acquired distinctiveness through use in appropriate cases. Evidence should demonstrate that relevant consumers identify the sign with the applicant, not merely that the icon has existed. Duration, geographic reach, downloads, advertising, user recognition, sales or subscriptions, press coverage and consistent use can be relevant.

Section 11 concerns earlier rights and likelihood of confusion, including identity or similarity of marks and the relationship between the goods or services. For icons, the analysis may involve overall visual impression, dominant elements, conceptual resemblance, accompanying words, the relevant consumers and the market context.

No. A conflict can arise from a similar overall impression even where details differ. Search and clearance should consider dominant symbols, composition, visual rhythm, stylisation, word elements, conceptual association and the proximity of the goods or services.

C. Filing Format, Use Claims, Fees and Evidence

An ordinary application is filed in Form TM-A. A single application can cover more than one class, but the official fee is payable for each class and each mark according to the current fee schedule.

The current official e-filing fee is ₹4,500 per class per mark where the applicant qualifies as an individual, startup or small enterprise, and ₹9,000 per class per mark in other cases. Eligibility for a concession should be documented rather than assumed.

Rule 26 requires a clear and legible representation of the trademark not exceeding the prescribed 8 cm by 8 cm size. The filed image should show the mark for which protection is actually sought and should avoid unnecessary app-store frames, screenshots, descriptive text or third-party platform elements that are not intended to form part of the trademark.

A proposed-to-be-used application does not assert prior market use. If use before the application date is claimed, Rule 25 requires the period and user to be stated and requires an affidavit testifying to that use together with supporting documents. The filing basis should reflect the evidence available.

Not merely for that reason. Trademark use concerns use of the sign in relation to the relevant goods or services. Internal creation, private design approval or an unpublished file may establish chronology or copyright evidence but does not automatically establish trademark use in the market.

Potentially, if the app was genuinely offered under the icon in relation to the claimed goods or services and the date is supported by reliable evidence. The earliest public listing should not be used mechanically where the listing was a closed test, dormant page or otherwise did not amount to the claimed commercial use.

Useful evidence can include dated app-store pages, release-console records, archived website pages, screenshots showing the icon and service offering, advertisements, customer or user communications, contracts, invoices, subscription or transaction records, analytics, press coverage and other contemporaneous documents. The evidence should connect the exact icon, date, applicant or authorised user, and claimed goods or services.

No. It should claim the earliest date that can be truthfully and coherently supported. An aggressive but poorly documented date can create examination, opposition, rectification, credibility and enforcement problems later.

Potentially, depending on the legal relationship and the Trade Marks Act provisions concerning permitted use. The applicant should document control, authorisation and the relationship rather than assume that use by any related business automatically counts as use by the proprietor.

The filing requires accurate applicant identity and address details. Where the reduced fee is claimed as a startup or small enterprise, the applicant should retain the documents supporting that status. Where a representative is appointed, the required authorisation should be properly executed in accordance with current Registry practice and applicable stamp requirements.

No. A word mark and a device mark are separate marks and ordinarily require separate applications and fees. A multi-class application also attracts the prescribed fee for each class.

Usually no. The specification should identify the actual goods or services in accepted classification language. “Mobile app services” can be too vague because downloadable software, SaaS, financial services, communications, education, marketplace services and other offerings can fall in different classes.

D. Colour Strategy, Ownership, Third-Party Assets and Icon Changes

There is no automatic rule that a black-and-white filing is always broader or better. The application should reflect the sign the business intends to protect. If a combination of colours is claimed as a distinctive feature, Rule 26 requires the mark to be reproduced in that colour combination. Where colour is not central to brand identity, the filing strategy should be assessed against actual use, expected variants and enforcement needs rather than relying on a blanket monochrome rule.

Not always. Minor colour or presentation changes may leave the essential identity of the mark intact, but the answer depends on what was filed and whether colour or other features are distinctive. Businesses using materially different icon variants should assess whether separate applications are justified.

A registered mark can only be altered through the statutory mechanism where the proposed addition or alteration does not substantially affect the identity of the mark. A redesign that changes the dominant symbol, lettering or overall commercial impression should usually be treated as a candidate for a fresh search and application.

The answer depends on the Copyright Act’s first-ownership rules, the nature of the commissioned work and the contract. Payment alone should not be treated as a universal transfer of copyright. Where the startup requires ownership, the chain should be documented clearly through an appropriate written assignment or other rights instrument.

No. An NOC can record consent to specified acts, but it does not automatically transfer copyright ownership. A copyright assignment must satisfy the statutory writing and signature requirements and should identify the work, rights assigned, duration, territory and consideration or other required terms.

Trademark and copyright ownership are separate questions, but the applicant should have a lawful basis to adopt and use the icon as a trademark. Filing a mark built from artwork owned by another person without adequate rights can create copyright, contractual and enforcement problems even if the trademark application itself proceeds.

Only after checking the licence carefully. Many stock and template licences restrict use as a trademark, logo, service mark or exclusive brand asset. A licence permitting ordinary commercial display does not necessarily permit exclusive trademark registration.

Potentially only if the relevant licence and surrounding rights permit the proposed use and exclusivity, and the sign itself is distinctive and available. Open-source terms can impose attribution, share-alike or other conditions that may be incompatible with the intended trademark strategy. The exact licence must be reviewed.

Potentially, but trademark filing does not resolve copyright authorship or provenance. The business should preserve the creation workflow, prompts and source assets where relevant, check the tool terms and third-party inputs, and ensure the final sign does not conflict with earlier trademarks or copied protected material.

The commercial chain should be documented and aligned. A founder, employee or agency should not retain uncontrolled ownership of essential developer credentials, domains or brand accounts after the relationship ends. Written agreements should address account ownership, administrator access, recovery credentials, handover and use of the trademark.

E. Copycat Apps, Enforcement, Copyright, Designs, Renewal and International Protection

A registration can provide a stronger statutory basis for infringement claims and can support platform intellectual-property complaints. The claimant should still preserve the exact copycat listing, screenshots, app name, icon, developer identity, package or bundle identifier, advertisements, dates and any evidence of confusion. Registration does not guarantee automatic app-store removal.

Potentially through passing off if the claimant can establish goodwill, misrepresentation and damage or likely damage. Copyright may also protect original icon artwork. The evidentiary burden and remedies differ from registered-trademark infringement.

A device-mark infringement or passing-off analysis can still be relevant because comparison is not limited to words. The overall visual impression, dominant features, related goods or services, user attention and likelihood of confusion should be assessed. Copyright can provide an additional route where the artwork itself was copied.

The app’s word mark may be the stronger right in that situation. Separate word-mark protection can therefore be commercially important. The complaint should identify the right actually infringed rather than use an icon registration as a substitute for an unregistered word claim.

No. Platform complaints can provide practical removal or account action under the platform’s rules, but they are not final adjudications of trademark infringement. Court relief may still be required for injunctions, damages, disclosure, domain or business relief, or repeated conduct outside the platform.

Yes, where the icon contains qualifying original artistic expression and the claimant owns or controls the relevant copyright. Copyright can address copying of the artwork even where trademark confusion is difficult to establish. The claimant should prove authorship or ownership and identify the protected expression actually copied.

Potentially, but the route remains fact-sensitive. In NEC Corporation v. Controller of Patents and Designs and connected appeals, decided on 9 March 2026, the Calcutta High Court held that graphical user interfaces are not per se excluded from design registration and that qualifying GUI features can be assessed under the Designs Act when properly applied to an article and not excluded by the statutory tests. The Court set aside the refusal orders and remanded the applications for fresh consideration; it did not automatically register every GUI or icon.

No. The judgment rejects a categorical exclusion of GUIs but preserves the statutory, case-by-case inquiry. The proposed design must still satisfy the requirements relating to an article, registrable design features, industrial application, eye appeal, novelty or originality and the statutory exclusions. Current Design Office practice should be checked before filing.

The ™ symbol is commonly used to signal a trademark claim and is not confined to registered marks. The ® symbol should be reserved for a mark that is actually registered in the relevant jurisdiction and should not be used in a way that falsely represents unregistered matter as registered. Section 107 of the Trade Marks Act penalises false representation of a trademark as registered.

Registration is for ten years and can be renewed for successive ten-year periods. Under Section 23, once registered, the registration ordinarily dates from the application date, subject to the Act. Renewal, surcharge and restoration mechanisms have their own prescribed periods and fees.

Section 47 provides more than one non-use ground. One can arise where the mark was registered without a bona fide intention to use it and there has in fact been no bona fide use. Another concerns a continuous five-year period of non-use from the date on which the mark is actually entered in the register, measured up to a date three months before the non-use application. The common “five years and three months” shorthand should therefore be understood through the exact statutory test rather than treated as a single standalone formula.

No. Trademark rights are territorial. Protection in other countries generally requires national or regional filings or an international filing strategy, including the Madrid Protocol where appropriate. Filing priorities should reflect actual launch markets, revenue, investor requirements, enforcement risk and budget.

F. Pre-Filing Strategy, Records and Common Mistakes

Confirm who created the artwork and who owns or controls the necessary rights; search the icon, words and relevant visual elements; identify the downloadable software and underlying service classes; review stock, template, open-source or AI provenance; decide the intended colour and variant strategy; and check app-store, domain and social-handle availability before investing heavily in launch.

Keep the filed representation, TM-A and acknowledgments, use affidavit and exhibits if applicable, search records, design source files, copyright or assignment documents, app-store launch evidence, advertising and transaction records, examination and opposition correspondence, renewal records, icon-version history and platform enforcement records. A clean evidence archive makes later opposition, non-use and enforcement work easier.

Common mistakes include filing a generic pictogram without a distinctiveness assessment; assuming Classes 9 and 42 are automatically sufficient; using vague goods or services wording; claiming an unsupported first-use date; omitting the Rule 25 affidavit and evidence for prior use; treating a designer’s NOC as copyright ownership; filing stock or template material without checking trademark restrictions; assuming black-and-white automatically gives unlimited colour protection; failing to file the app name separately where commercially important; and assuming app-store acceptance or trademark registration guarantees takedown of copycats.

Identify the correct proprietor; clear copyright and third-party artwork rights; freeze the icon version to be filed; decide whether colour is claimed; identify the actual Nice classes and precise goods or services; run word, phonetic, Vienna and visual searches plus market searches; choose proposed-to-be-used or a defensible prior-use claim; prepare the required use affidavit and supporting documents where prior use is claimed; align developer accounts, domains and social handles; consider separate word-mark protection; preserve launch evidence; and identify priority foreign markets before publication or expansion.

If you have a proposed or existing app icon and need matter-specific review of clearance, filing basis, ownership documents or enforcement options, you may send a preliminary enquiry.

Last reviewed: 12 September 2026