China software copyright registration can provide useful evidence, but it does not create copyright or conclusively settle ownership. Before preparing a filing, identify the software version, check who owns the relevant rights and decide how confidential code will be handled. The registration rules provide exceptional deposit and sealing mechanisms; they do not authorize unlimited redaction or guarantee confidentiality throughout every transfer.
For a software business working across borders, the immediate question is practical: what should be established before anyone sends a repository, technical document or contract?
What does a software registration certificate prove?
Under Articles 7 and 14 of the Computer Software Protection Regulations, copyright arises when eligible software development is completed, and a registration certificate is preliminary evidence of the registered matters. Treat the certificate as part of an evidence file, rather than a final decision about competing rights.
Articles 2–6 address programs and related documentation, independent development and fixation. Protection does not extend to the ideas, processing procedures, operating methods or mathematical concepts used in development. Registration therefore does not give its holder exclusive rights over every product performing the same function.
A filing should identify the particular software expression and version being claimed. A broad product description cannot resolve whether another business copied protected material.
Check foreign eligibility and the ownership chain
Article 5 covers foreign and stateless developers through first distribution in China or applicable agreements and international treaties. Check the relevant connection; foreign incorporation alone is not the full eligibility analysis.
The ownership rules also need attention. Article 11 addresses written agreements for commissioned development, with ownership belonging to the commissioned developer where there is no agreement or no clear allocation. Article 13 sets conditions for organization ownership of employee-developed software. Neither “we paid for it” nor “an employee wrote it” answers every case.
Prepare a creator-to-applicant map before selecting material. Identify the entities, employees, contractors and any transfers involved. Separate your own contributions from licensed components. Access to a repository does not establish ownership of everything inside it, and open-source permissions need their own review.
Match the version, code and documentation
Articles 9–11 of the Software Copyright Registration Measures address the application, identifying materials and supporting documents. Under the ordinary Article 10 route, the source program and one selected document each provide the first and last 30 consecutive pages. If either is shorter than 60 pages, that material is provided in full. These are separate code and documentation requirements, not a combined 60-page allowance.
Start with a version sheet: software title, version identifier, development completion information, applicant name and the records supporting them. Check that the selected documentation describes that version. A current user manual paired with a different release's code can create avoidable uncertainty.
Keep a private index linking each proposed file to its origin and version. Resolve inconsistent names and unexplained entity changes before submission; do not silently edit historical records to make them appear consistent.
Plan confidentiality before choosing deposit materials
Article 12 offers specified exceptional deposit alternatives. One permits confidential portions of the first and last 30 source-code pages to be covered with black broad diagonal lines, capped at 50% of the deposited source. Other alternatives use specified source-code selections or object code combined with source code; documentation can also use exceptional deposit by reference to these rules.
Article 13 allows an application to seal source code, documentation or samples; only the applicant or judicial authorities may unseal them. Article 26 separately permits inspection of registration announcements and publicly disclosable related documents. That is not a statement that every submitted file is publicly accessible.
Choose an appropriate route before preparing the submission. Do not assume that calling a file “confidential” permits arbitrary omissions, or that sealing removes every disclosure risk. Consider who receives material before filing, who can access working copies and how files will be retained or deleted.
Confirm the current China Copyright Protection Center submission channel, document format and handling of exceptional deposits or sealing. The legal provisions alone do not establish today's portal workflow. A page-count summary is not a substitute for checking the selected route's requirements.
Preserve evidence beyond the certificate
The following are practical preparation suggestions, not a universal statutory filing checklist:
Version identity: preserve release records, repository history and the documentation associated with the claimed version. Explain migrations and gaps rather than relying only on a screenshot of the latest branch.
Development and entitlement: retain dated project records and the relevant employment, commissioning, assignment or authorization documents. Connect each document to the applicant and the software concerned.
Component boundaries: record third-party libraries, licensed material and open-source components, together with relevant permissions. Distinguish material you own from material you are entitled to use.
File integrity: retain originals and an index of versions, dates and file hashes where useful. A hash can help compare files; it does not, by itself, prove authorship, ownership or when a file was created.
Keep registration preparation separate from an infringement response. If copying is already suspected, preserve the public links, product details and relevant notices for a separate China IP enforcement assessment. Avoid changing the only surviving evidence while assembling a filing package.
Start with a nonconfidential software inquiry
Our China copyright registration overview discusses standard work categories. Software inquiries require separate confirmation of scope and service availability; do not assume the same materials or procedure apply.
For an initial discussion, provide the software's general purpose, title and version, proposed owner's legal name, the China-related issue, budget and deadline. A public product link can help explain the context.
Arrange a conflict check, confidentiality terms and a secure transfer channel before sharing source code, private repositories, proprietary technical documents or confidential contracts. An initial discussion is not a formal ownership or infringement opinion.
Official sources checked November 4, 2026. This guide provides general information; eligibility, ownership, deposit choices and current submission requirements need review for the particular software.