Home > Resources > Copyright FAQs > UI/UX & Screen Design Copyright FAQs
UI/UX & Screen Design Copyright FAQs
India │ Copyright, design registration, ownership, code, UI assets, AI-assisted design, evidence and enforcement for app screens, GUIs, wireframes and digital product interfaces.
Purpose and Scope. A UI/UX matter can involve several different rights. Copyright may protect original code, text and artwork; design registration may protect eligible visual features applied to an article; trademark and contract/confidentiality can protect different interests. The correct route depends on the work, ownership chain, industrial application, disclosure history and evidence. Current statutory text, Copyright Office and Designs Office practice, and relevant case law should be checked before filing or enforcement.
A. Copyright Protection for UI, Screens and Software
Not as a single undifferentiated concept. A graphical user interface can contain several different kinds of subject matter: source and object code may qualify as a computer programme and therefore a literary work; original illustrations, icons, drawings or graphic artwork may qualify as artistic works; and sufficiently original text may qualify as literary work. The general idea of the interface, its function, workflow, business logic or familiar screen arrangement is not automatically monopolised by copyright.
Yes. The code that causes the interface to operate can be protected as a computer programme, while original visual or textual elements displayed on the screen can raise separate copyright questions. Ownership of the code does not automatically prove ownership of every logo, icon, illustration, font, photograph or other visual asset used in the interface, and ownership of a screen artwork does not automatically transfer ownership of the underlying software.
There is no automatic copyright monopoly over an abstract “look and feel”. A claimant should identify the particular protectable expression alleged to have been copied and separate it from functionality, ideas, common conventions, public-domain material and independently created elements. A sufficiently original selection or arrangement can matter, but similarity in overall impression alone does not answer the legal question.
Copyright does not protect an idea, method, system or business logic merely because it is reflected in a particular user journey. A checkout sequence, onboarding flow, swipe interaction, dashboard logic or navigation concept may be functionally valuable without creating an exclusive copyright over the method itself. Copyright can protect the particular original expression used to implement or depict the flow.
Generic menus, standard tabs, ordinary search bars, familiar button placement, conventional forms, common icons, standard gestures, functional labels, usual mobile navigation patterns and other elements constrained by function or established practice are generally weak foundations for an exclusive copyright claim. The analysis should focus on original expressive features rather than merely similar functionality.
Potentially. An original icon, illustration, diagram or other graphic can qualify as an artistic work if the statutory requirements are satisfied. Protection concerns the original expression embodied in the artwork, not the underlying function represented by the symbol. A generic or familiar symbol may have little protectable expression even though a highly original rendering could be protectable.
Sufficiently original screen text can qualify as literary work, but very short functional labels, commands and routine phrases may have too little original expression to support a meaningful copyright claim. Longer onboarding text, explanatory content, help material or original copy should be assessed separately from ordinary interface commands.
A wireframe or prototype may contain protectable original drawings, text, artwork or other expression even though it is not the final product. Low-fidelity functional structures are likely to contain a larger proportion of unprotectable ideas and conventions. The evidentiary value of wireframes is often significant because dated versions can show how the final interface developed.
No. Copyright in a qualifying original work ordinarily arises by operation of law; registration is not what creates the copyright. Registration can nevertheless provide a useful official record and evidentiary trail. It should not be treated as a Government determination that every element is original, owned by the applicant or infringed by another party.
B. Copyright Registration for Apps, Screen Displays and Design Assets
The Copyright Office currently states that an app may be registered as a computer programme under the literary-work category because Section 2(o) includes computer programmes within literary works. Its current FAQ and Literary Works Manual require the prescribed software material, including source code and object code, in accordance with the applicable Copyright Rules. Software registration should therefore be distinguished from registration of a separate artistic or other asset used in the interface.
Current Copyright Office guidance states that registration of the computer programme can cover screen displays generated by that programme where the code generating the display is submitted and the owner of the computer programme and the screen display is the same. This is an administrative registration position; it does not mean that unrelated third-party visual assets are automatically absorbed into the software claim.
No, not as a substitute for the software-registration requirements. Current Copyright Office guidance states that mere snapshots of app screen displays are not eligible for registration as the computer programme. A screenshot may still contain separately protectable text, artwork, photographs or other material, but those components require their own legal and ownership analysis.
Potentially, if it qualifies independently as an artistic work and the applicant can establish authorship and ownership. The work claimed should be identified precisely. Filing the software and separately filing important artistic assets can involve different classes of copyright work and different supporting documents.
Not necessarily. Current Copyright Office guidance treats websites and apps as containing multiple components that may fall into different copyright categories. Software, text, photographs, artwork, audio and other elements can have different authors and owners. The registration strategy should therefore identify the specific work being claimed rather than assume that one filing automatically captures every component of a digital product.
No. Possession or control of a source-design file is evidence of access and can be useful in proving creation history, but ownership depends on authorship, employment, assignment, licence and other legal facts. A client can possess a working file without owning all copyright in it, and a designer can retain a copy of a file after assigning the economic rights.
Preserve dated source files, version history, authorship records, contributor contracts, assignment or licence documents, third-party asset licences, first-publication information, software code where relevant, and evidence identifying the exact work claimed. The registration file should be consistent with the project’s actual ownership chain.
C. Design Registration, GUI Protection and Copyright–Design Overlap
Potentially, yes. In NEC Corporation v. Controller of Patents and Designs and connected appeals decided on 9 March 2026, the Calcutta High Court rejected a per se bar against GUI design registration, set aside the refusals before it and remanded the applications for fresh consideration. The Court held that GUIs may be registrable case by case when the requirements of Sections 2(a) and 2(d) of the Designs Act, 2000 are satisfied and the design is properly identified with an article; the decision does not make every GUI automatically registrable.
The claimed visual features must satisfy the Designs Act requirements in the particular case. The applicant should identify the article to which the GUI design is applied, establish novelty or originality, show visual features capable of appeal to and judgment solely by the eye, and avoid a claim whose appearance is dictated solely by function. Section 4 grounds and other statutory requirements must also be satisfied.
No. The 2026 Calcutta High Court decision explains that the design and the article are distinct concepts. Depending on the facts, the relevant article may be a display unit, screen, phone, tablet, vehicle dashboard or another product to which the GUI is applied. The GUI need not itself be manufactured or sold as a separate physical object.
Not merely for that reason. The Calcutta High Court rejected permanence and always-visible requirements that are not found in Section 2(d). A GUI displayed during the intended or normal use of an article can still be assessed for design registration, but the statutory requirements—including visual appeal, article identification and the exclusion of features dictated solely by function—still have to be met.
The current Locarno classification includes Class 14-04 for screen displays and icons, including graphical user interfaces and computer icons. Rule 10(1) of the Designs Rules uses the current Locarno classification for classification purposes. The Calcutta High Court has stressed that this classification is administrative and indicative only: inclusion in Class 14-04 does not itself establish registrability under Sections 2(a) and 2(d) of the Designs Act.
Section 4 of the Designs Act bars registration where a design lacks novelty or originality or has been disclosed to the public before the relevant filing or priority date in the circumstances covered by the Act. Public launches, published screenshots, unrestricted demonstrations or other public disclosure can therefore create serious novelty problems, subject to any applicable statutory exception. Design protection should be assessed before public disclosure where it is commercially important.
Section 15(1) of the Copyright Act provides that copyright under that Act does not subsist in a design registered under the Designs Act, 2000. The same subject matter should therefore not be assumed to receive full parallel Copyright Act and registered-design protection. The precise artistic work and the precise design claimed must be identified separately.
Section 15(2) of the Copyright Act provides that copyright in such a design ceases once an article to which the design has been applied has been reproduced more than fifty times by an industrial process by the copyright owner or with the owner’s licence. Whether the provision applies is fact-sensitive: the court must classify the subject matter, determine whether it is a design capable of registration and examine the relevant industrial reproduction.
No. The Supreme Court in Cryogas Equipment Pvt. Ltd. v. Inox India Ltd. (2025) emphasised that Section 15(2) requires a classification exercise and framed a two-pronged inquiry distinguishing a pure artistic work from a design derived from such work and subjected to industrial process, followed where necessary by a functional-utility analysis. Copyright in an original artistic work should not be assumed to disappear mechanically merely because a related design is industrially exploited; the particular work and design must be analysed separately.
Section 11 of the Designs Act gives the registered proprietor copyright in the registered design for ten years from the date of registration, with one further five-year extension available on a timely application and payment of the prescribed fee. The ordinary maximum term is therefore fifteen years, subject to the Act and Rules.
Not by itself. Brand names, logos and other source identifiers require trademark and passing-off analysis. An original logo artwork can also contain copyright, but copyright ownership does not replace trademark clearance, trademark filing or evidence of market use.
D. Ownership, Employees, Freelancers, Agencies and Contracts
Section 17 contains the first-ownership rules. For a work made in the course of employment under a contract of service or apprenticeship, Section 17(c) ordinarily makes the employer the first owner in the circumstances covered by that provision, unless there is an agreement to the contrary. The actual employment relationship, scope of duties, type of work and contract should still be checked.
Not as a general rule. The Copyright Act contains specific first-ownership exceptions for some commissioned works, but payment of an invoice does not by itself amount to a general assignment of all copyright in every commissioned digital design. Outside an applicable statutory exception, the creator may remain the first owner unless the necessary rights are assigned or licensed. The contract should therefore address ownership expressly.
Not necessarily. The client should verify whether the agency itself owns or is authorised to transfer the relevant rights from employees, consultants and subcontractors. The contract should contain an appropriate chain-of-title mechanism and should identify third-party and pre-existing materials that are licensed rather than assigned.
Section 19 requires an assignment to be in writing and signed by the assignor or an authorised agent. It must identify the work and specify the rights assigned, duration and territorial extent, and it must deal with royalty or other consideration as required by the Act. If duration is not stated, the statutory default is five years; if territory is not stated, the default is India.
An assignment transfers the specified copyright rights to the assignee, while a licence permits specified uses without transferring ownership of those rights. A UI project can require a mixture: commissioned original screens may be assigned, while fonts, stock illustrations, icon libraries, frameworks and templates may remain subject to third-party licences.
No. File delivery and copyright ownership are separate issues. A contract can require delivery of editable Figma, Sketch, XD, Illustrator or source-code files while granting only a licence, or it can assign copyright without transferring every proprietary tool or library. The agreement should address both ownership and deliverable control explicitly.
Joint authorship should not be assumed merely because several people participated. The Copyright Act’s concept of a work of joint authorship turns on collaborative production where the contribution of one author is not distinct from the contribution of the other author or authors. In practice, map each creative contribution and secure the required rights from every relevant contributor while identifying pre-existing and third-party material.
Not merely because the company paid for or customised it. A third-party licence may permit commercial use, modification or distribution while reserving ownership in the underlying asset. The company may own original additions or a protectable arrangement, if any, without acquiring ownership of the pre-existing component itself.
The agreement should identify deliverables and versions; source and editable files; authorship and ownership; assignment or licence; pre-existing and third-party materials; modification rights; sublicensing; fonts and stock assets; confidentiality; warranties; design-system components; open-source software; portfolio use; handover; termination; enforcement cooperation; and treatment of future updates and derivative versions.
Section 57 gives authors specified special rights, including the right to claim authorship and to restrain or claim damages for prejudicial distortion, mutilation or modification in the statutory circumstances. Economic assignment should therefore not be assumed to erase every authorial right. Contract drafting should address attribution and modification with the statutory framework in mind.
Only if the contract and confidentiality position permit it. Copyright ownership, possession of the design files and permission to disclose unreleased or confidential work are separate questions. A portfolio clause should address timing, approved images, attribution, redaction of customer or security data and any removal obligation.
E. AI, Third-Party Assets, Confidentiality and Product Governance
The project should record the human creative contribution, tool used, applicable service terms, prompts where appropriate, selection, editing and provenance of the output. Section 2(d)(vi) contains a statutory authorship rule for computer-generated literary, dramatic, musical and artistic works, but how that rule applies to modern AI-assisted or highly autonomous generation can raise unresolved questions of authorship, originality and ownership. Important assets should not be treated as unquestionably proprietary merely because an AI tool produced them.
No. An AI output can resemble third-party material, contain familiar or unprotectable elements, or be subject to contractual restrictions in the AI service terms. Important production assets should be reviewed for provenance, similarity risk, permitted commercial use and the degree of meaningful human authorship or modification before they are treated as proprietary IP.
Open-source software is governed by its licence. The team should preserve the licence, version and source of each component and check attribution, notice, redistribution, source-disclosure and modification obligations. Copyright ownership in the company’s UI does not override third-party obligations attached to incorporated code.
Keep the supplier, licence, version, date of acquisition, permitted users, permitted products, modification rights, redistribution limits and attribution requirements. A design handover should distinguish owned assets from licensed assets so that a later buyer, investor or replacement developer knows which materials cannot be freely transferred.
Potentially. Section 16 of the Copyright Act expressly preserves rights and jurisdiction to restrain breach of trust or confidence, and contractual confidentiality can protect non-public prototypes, source files, research and product plans. Confidentiality is distinct from copyright and can be important where the material is functional, commercially sensitive or otherwise presents a weak copyright claim.
Screenshots used for design review, evidence, portfolios or legal proceedings can contain names, account details, health information, financial information, location data, authentication material or other personal or confidential data. The evidence or portfolio copy should preserve what is legally necessary while using appropriate redaction, access control and data-handling procedures.
Record each important screen set, design system, source file, codebase, icon set, font, illustration, photograph and external library; identify the author, owner, licence, assignment, creation date, version, publication date and repository location; and link the relevant contract. The register should also flag design-registration candidates before public disclosure and record AI-assisted material separately where provenance matters.
F. Clone Apps, Infringement Evidence and Enforcement
The claimant must identify the copyright work, establish title, show the relevant exclusive right and prove copying or other infringing conduct concerning protectable expression. The comparison should filter out ideas, methods, functions, common UI conventions, licensed material and independently created features. A screen-by-screen resemblance can be relevant but is not by itself the legal test.
No. Reproducing an idea, function, business method or user journey is not automatically copyright infringement. Liability depends on whether protectable expression—such as original code, artwork, text or another protected component—has been copied in a legally material way.
Not merely because it performs the same function. Copyright in a computer program protects expression in the code and related protected material, not the abstract idea or functionality of the software. Evidence of copied source code, object code, structure or another protectable element presents a different issue from independently implementing the same concept.
Preserve dated screenshots and full screen recordings, app-store or website listings, URLs, version numbers, download files where lawful, device and operating-system details, publication dates, archived pages, the claimant’s earlier source files and version history, source-control logs, launch records, contracts and third-party licences. The evidence should make the comparison reproducible rather than depend on memory or a few cropped images.
No. Registration is not the source of copyright, and the Copyright Act does not make registration a general condition for copyright to subsist. A registration entry can assist recordkeeping and evidentiary presentation, but a claimant still has to establish the protectable work, title, the relevant exclusive right, infringement and the basis for any relief sought.
Section 55 provides civil remedies that can include injunction, damages, accounts and other relief, subject to the statutory conditions and limitations. The appropriate remedy depends on the facts, proof, urgency, commercial harm and the conduct complained of. A platform takedown request or cease-and-desist letter is not itself a substitute for establishing the legal elements of infringement.
Yes, in the circumstances defined by the Act. Section 63 applies where a person knowingly infringes or abets infringement of copyright or specified other rights. Criminal allegations should not be made merely because two products look similar; the protected work, ownership, infringing conduct and knowledge element require careful factual assessment.
No. A platform may restrict or remove content under its own complaint procedure, but that administrative action is not a final judicial determination of copyright ownership or infringement. A complainant should present accurate rights information, and the responding party should preserve the notice, counter-notice, evidence and platform decision.
Trademark and passing off can protect branding and source identifiers; the Designs Act can protect an eligible registered GUI or other design; contract and confidentiality can govern shared prototypes, files and development relationships; and data-protection obligations can apply where user information is involved. The legal route should match the right and conduct actually in issue.
Common mistakes include treating functionality as copyright; assuming screenshots alone constitute software registration; failing to assess GUI design registration before public disclosure; ignoring Section 15 copyright–design overlap; relying on an agency invoice instead of a written rights transfer; failing to collect freelancer and subcontractor assignments; losing Figma and version history; using fonts, stock assets or open-source components without licence records; claiming AI-assisted output without provenance review; and sending a clone-app allegation without first separating protected expression from common UI conventions.
Maintain one evidence-led IP file linking each important screen and design asset to its creator, source file, version history, ownership document, third-party licence, publication date, design-registration decision and actual product use. For a dispute, add a reproducible comparison of the competing product and identify separately the code, artwork, text, design, trademark, contract and confidentiality rights relied upon. This produces a materially stronger basis for registration, licensing, due diligence or enforcement than a general claim that the overall interface was copied.
If you are assessing ownership, registration, a proposed launch or a suspected clone interface requiring matter-specific review, you may send a Preliminary Enquiry.
Subject to conflict check, scope confirmation, professional terms and express acceptance by Analysta Juris Legal Solutions.
Last reviewed: 13 September 2026