Paying for a logo, website, app, video, architectural rendering, engineering drawing, or other creative or technical work does not automatically mean you can demand the source files in the Philippines. The answer depends mainly on what your contract, quotation, purchase order, invoice, chat messages, or email thread says were included. Under Philippine law, payment usually gives you the deliverable you agreed to buy. Editable files, raw files, source code, working files, and project repositories are often treated as separate deliverables unless they were clearly included or are necessary to fulfill the agreed purpose of the project.
This matters because many disputes start only after the final output is delivered. A business owner receives a JPEG logo but later asks for the Adobe Illustrator file. A client pays for a website but later asks for the full source code and database. A homeowner pays for 3D renders but asks for the editable CAD or SketchUp files. A startup pays a developer but discovers the code is hosted in the developer’s private GitHub account. In each case, the legal issue is not just “I paid, so I own everything.” The better question is: what exactly was sold, licensed, assigned, or promised?
What Are “Source Files” in Creative and Technical Work?
“Source files” is a practical business term, not a single defined term under Philippine statutes. It usually refers to the editable or working version of a project that allows another person to modify, rebuild, export, or continue the work.
Common examples include:
| Type of work | Final deliverable | Possible source files |
|---|---|---|
| Logo design | PNG, JPEG, PDF | AI, PSD, SVG, EPS, Figma file |
| Website | Live website, exported HTML pages | Full source code, CMS access, theme files, database, repository |
| Mobile app | APK, IPA, deployed app | Source code, build files, credentials, API documentation |
| Video editing | MP4 file | Premiere Pro, DaVinci Resolve, After Effects project files, raw footage |
| Photography | Edited JPEGs | RAW files, Lightroom catalog |
| Architecture/interior design | Rendered images, PDF plans | CAD, DWG, SKP, BIM, editable 3D model |
| Software automation | Working script or compiled tool | Code repository, configuration files, deployment instructions |
The practical value of source files is high. They allow the client to:
- edit the work without returning to the original creator;
- hire another designer, developer, editor, or engineer;
- reproduce or adapt the work in other formats;
- maintain a website or app after the project ends;
- avoid being locked into one vendor.
Because of this value, many freelancers, agencies, developers, and studios price source files separately.
The Basic Rule: Check the Agreement First
Under the Civil Code of the Philippines, Article 1159, obligations arising from contracts have the force of law between the parties and must be complied with in good faith. Article 1305 defines a contract as a meeting of minds where one person binds himself to give something or render a service, while Article 1306 allows parties to agree on terms as long as they are not contrary to law, morals, good customs, public order, or public policy.
In plain English: your contract controls.
A “contract” does not always mean a long notarized document. In real Philippine transactions, especially with freelancers and small businesses, the agreement may be found in:
- signed service agreements;
- quotations or proposals accepted by email;
- purchase orders;
- invoices;
- Viber, Messenger, WhatsApp, Telegram, Slack, or SMS exchanges;
- payment confirmations;
- project briefs;
- platform terms from Upwork, Fiverr, OnlineJobs.ph, Shopify, GitHub, Figma, or similar tools;
- statements like “package includes editable files” or “turnover includes source code.”
The E-Commerce Act of 2000, Republic Act No. 8792, recognizes electronic documents and electronic data messages in commercial and non-commercial transactions. This is important because Philippine courts and dispute forums can consider properly authenticated emails, chat messages, digital invoices, and electronic agreements as evidence.
Payment Alone Does Not Always Transfer Copyright
For creative and technical work, Philippine copyright law is often the most misunderstood part.
Under the Intellectual Property Code of the Philippines, Republic Act No. 8293, copyright protects original literary and artistic works from the moment of creation. Section 172 includes works such as drawings, paintings, works of art, illustrations, maps, plans, sketches, charts, technical drawings, photographic works, audiovisual works, advertisements, and computer programs.
Section 178 provides the key rule on ownership:
- For original works, copyright generally belongs to the author or creator.
- For employee-created works, the employer may own the copyright if the work was created as part of the employee’s regularly assigned duties, unless there is an agreement saying otherwise.
- For commissioned work by an independent contractor, the person who commissioned and paid for the work owns the work, but the copyright remains with the creator unless there is a written stipulation to the contrary.
That last rule is critical.
If you hired an independent graphic designer, web developer, photographer, video editor, architect, engineer, or software contractor, paying them may give you ownership of the commissioned output, but it does not necessarily transfer copyright or all editable working materials unless the agreement clearly says so.
Section 180 of RA 8293 also states that copyright is not deemed assigned during the lifetime of the owner unless there is a written indication of that intention. Section 181 further provides that copyright is distinct from the property in the material object. In practical terms, receiving a copy of the final logo, website, video, photo, or design does not automatically mean you received every copyright, editable file, raw file, or development file behind it.
“I Own the Work” vs. “I Own the Copyright” vs. “I Own the Source Files”
These are different rights.
| Issue | Meaning | Example |
|---|---|---|
| Ownership of the final work | You own the delivered item or commissioned output | You received the approved logo PNG and can use it for your business |
| Copyright ownership | You own the economic rights to reproduce, adapt, distribute, display, or license the work | You can modify the logo, sell derivative versions, or authorize others to use it |
| Source file possession | You physically or digitally receive the editable working files | You receive the AI, PSD, Figma, GitHub repo, CAD, or RAW files |
| License to use | You may use the work for a specific purpose even if you do not own copyright | You can use the website design for your company website but not resell the template |
| Moral rights | The creator retains certain personal rights, such as attribution and objection to prejudicial distortion | A designer may object if their name is attached to a heavily distorted version |
Under Sections 193 to 198 of RA 8293, authors also have moral rights, including the right to be attributed and to object to distortions or modifications that are prejudicial to their honor or reputation. These rights are separate from economic copyright and should be addressed carefully when a client plans to heavily modify creative work after receiving source files.
When Can You Legally Demand Source Files?
You have the strongest legal basis to demand source files when one or more of the following applies.
1. The Contract Clearly Says Source Files Are Included
This is the cleanest case.
Examples of clear language:
- “Package includes final logo files and editable Adobe Illustrator source file.”
- “Developer shall turn over the full source code repository upon full payment.”
- “All project files, raw footage, and editable files shall be delivered to the client.”
- “Upon payment, client shall own all work product, including source files, working files, code, documentation, and intellectual property rights.”
- “Final turnover includes admin credentials, database export, source code, deployment guide, and third-party account access.”
If the supplier refuses after agreeing to this, the issue becomes a breach of contract.
2. The Quotation or Proposal Lists Source Files as Deliverables
Many disputes are resolved by carefully reading the proposal. If the quote says “logo design package — includes PNG, JPEG, PDF, AI file,” the AI file is part of the paid deliverables.
If the quote says only “logo design — 3 concepts, 2 revisions, final PNG and JPEG,” the designer has a stronger argument that editable files were not included.
3. The Source Files Are Necessary to Make the Delivered Work Usable as Agreed
Even if “source files” were not named, there may be situations where turnover of certain files or access is necessary to fulfill the purpose of the contract.
For example:
- A developer was hired to build a custom website that the client’s in-house team would maintain.
- A software contractor was hired to create a custom internal tool, not merely provide a hosted service.
- A company paid for a custom app and needs the code repository to publish updates.
- An architect or designer was hired to produce plans that another licensed professional must continue or revise.
In these cases, the client may argue that the source files, credentials, or documentation are implied deliverables based on the nature and purpose of the engagement. Under Civil Code Article 1371, courts may consider the parties’ contemporaneous and subsequent acts to determine their intention. Article 1376 also allows usage or custom to help interpret ambiguities.
But this is fact-specific. The stronger your written evidence, the better.
4. The Supplier Used “Work for Hire,” “Full Buyout,” or “All Rights” Language
In the Philippines, people often use foreign-style phrases like “work for hire,” but the enforceability still depends on Philippine law and the actual wording.
A phrase like “full buyout” may help, but it is better if the agreement expressly states:
- source files are included;
- copyright is assigned;
- the client may edit, reproduce, adapt, publish, and transfer the work;
- all project files and credentials will be turned over upon full payment.
Because Section 180.2 of RA 8293 requires a written indication of copyright assignment, vague words can create disputes.
5. The Creator Is an Employee and the Work Was Part of Regular Duties
If the creator is an employee, not an independent contractor, Section 178.3 of RA 8293 may place copyright ownership with the employer if the work was created as part of the employee’s regularly assigned duties, unless there is an agreement saying otherwise.
For example, if a company’s employed graphic designer creates marketing layouts during work hours as part of the job, the company has a stronger claim over the work files than it would have against an outside freelancer.
This is different from hiring an independent contractor. Labels matter less than actual circumstances, but employment relationships are governed by a different analysis.
When You Usually Cannot Demand Source Files
You may have a weak claim if:
- the contract only promised final output, not editable files;
- the package specifically excluded source files;
- the creator’s terms say source files are available only for an additional fee;
- the supplier provided a licensed template, plugin, stock asset, font, or third-party code they cannot legally transfer;
- the file contains the creator’s proprietary methods, reusable internal templates, scripts, presets, libraries, or trade secrets;
- the work was delivered through a hosted service, not as a transfer of code or files;
- you are asking for raw files after accepting a package that only included edited outputs.
A common example is photography. Many photographers sell edited JPEGs, not RAW files. RAW files may be treated like digital negatives or working files. Unless the agreement includes RAW turnover, the client may not automatically be entitled to them.
Another example is web design using proprietary systems. If you paid for a website built on the agency’s own platform, your right may be to use the website, not to receive the agency’s entire platform code.
Source Code, Websites, and Apps: Special Practical Issues
For software and websites, the “source file” issue is often more serious because the client may be unable to maintain the product without access.
At minimum, a proper technical turnover should clarify:
- GitHub, GitLab, Bitbucket, or other repository access;
- database export;
- CMS admin credentials;
- domain registrar access;
- hosting control panel access;
- cloud provider access;
- API keys and third-party service accounts;
- build instructions;
- deployment instructions;
- documentation;
- list of paid plugins, themes, libraries, and licenses;
- whether the developer used open-source, proprietary, or third-party components.
Be careful with passwords, customer data, and production databases. If source files include personal data, the Data Privacy Act of 2012, Republic Act No. 10173, may apply. If access is taken without authority, or if someone changes credentials, deletes files, or interferes with a computer system, the Cybercrime Prevention Act of 2012, Republic Act No. 10175, may become relevant.
A client should avoid “self-help” tactics like guessing passwords, entering private repositories without permission, copying files from an account not assigned to them, or locking out the developer before clarifying rights. A supplier should also avoid holding hostage client-owned domains, hosting, paid accounts, or data unrelated to any legitimate unpaid balance.
What To Do If the Supplier Refuses To Release Source Files
1. Gather and Organize Your Evidence
Collect everything before sending accusations.
Useful evidence includes:
- signed contract or service agreement;
- quotation, proposal, invoice, and official receipts;
- screenshots of chat messages showing deliverables;
- emails discussing turnover;
- proof of payment;
- project brief;
- revision history;
- links to shared folders;
- platform terms if you hired through a marketplace;
- copies of the final files delivered;
- screenshots showing lack of access to the repository, hosting, or editable file.
For electronic messages, keep the original files or exports when possible. Screenshots help, but courts and agencies give more weight to properly authenticated records.
2. Identify Exactly What You Are Demanding
Do not simply say, “Give me all files.”
Be specific:
- “Adobe Illustrator source file of the approved logo”
- “Figma file for the approved UI screens”
- “GitHub repository containing the Laravel source code”
- “WordPress admin access and cPanel access”
- “database export as of project turnover date”
- “DWG files for the approved floor plan”
- “Premiere Pro project file and linked assets used for the final video”
This avoids confusion and makes the demand easier to evaluate.
3. Check Whether There Is an Unpaid Balance or Pending Acceptance
If the agreement says turnover happens only after full payment, confirm whether full payment has actually been made.
If there are disputed revisions, rejected deliverables, or unpaid change orders, separate the issues:
- What has already been paid?
- What deliverables correspond to that payment?
- What work is outside scope?
- What files are being withheld because of unpaid fees?
- Are both sides willing to use escrow or staged release?
Philippine courts generally look more favorably on parties who acted in good faith and tried to clarify obligations before escalating.
4. Send a Written Demand Letter
A demand letter should be calm, specific, and evidence-based.
It should include:
- the project name and date;
- the amount paid and payment dates;
- the deliverables agreed upon;
- the source files or access being requested;
- the legal or contractual basis;
- a reasonable deadline, commonly 5 to 10 business days;
- a request for confirmation if the supplier claims the files are excluded or require a separate fee.
Demand letters are often sent by email first. For stronger evidentiary value, they may also be sent by courier or registered mail. Notarization is not always required, but a notarized demand letter can be useful when the dispute may proceed to court, especially for proving that a formal demand was made.
5. Consider Barangay Conciliation If Required
If both parties are natural persons who live in the same city or municipality, or in adjoining barangays of different cities or municipalities and they agree to submit the dispute, the Katarungang Pambarangay system may apply before filing in court.
The legal basis is the Local Government Code of 1991, Republic Act No. 7160. The Supreme Court has emphasized through Administrative Circular No. 14-93 that prior barangay conciliation is a pre-condition for many covered disputes.
Barangay conciliation usually does not apply when one party is a corporation, partnership, or other juridical entity. It also does not apply to all disputes, especially those requiring urgent court action or involving parties outside the required residence rules.
If a settlement is reached, put the source-file turnover terms in writing:
- exact files;
- format;
- folder or repository;
- deadline;
- payment, if any;
- who owns or may use the files;
- confidentiality and data-handling obligations;
- consequence for non-compliance.
A barangay settlement may later be enforced under the rules on barangay settlements if not repudiated within the allowed period.
6. Choose the Correct Legal Route
The proper route depends on what you want.
| Goal | Possible route | Practical note |
|---|---|---|
| Refund or unpaid money not exceeding ₱1,000,000 | Small claims before first-level courts | Small claims are designed for money claims, not usually for forcing source-file turnover |
| Damages for breach of contract | Civil action | May require regular or summary procedure depending on amount and relief |
| Delivery of specific source files or access | Civil action for specific performance and/or damages | More complex than small claims |
| Copyright infringement | Court action or IPOPHL administrative complaint, depending on facts | Not every file-turnover dispute is copyright infringement |
| IP dispute with damages of at least ₱200,000 | IPOPHL Bureau of Legal Affairs administrative complaint may be relevant | IPOPHL handles certain IP violations, not ordinary collection disputes |
| Mediation of an IP dispute | IPOPHL mediation | IPOPHL mediation periods may run around 60 days, extendible in proper cases |
| Cyber access, deletion, hacking, credential misuse | Criminal complaint may be relevant | Requires facts showing more than ordinary breach of contract |
The Supreme Court’s Rules on Expedited Procedures in First Level Courts increased the small claims threshold to ₱1,000,000. Small claims can be useful if your practical goal is to recover money. But if your main goal is to compel turnover of source code, editable files, or credentials, small claims may not be the best fit because it is generally for money owed under contracts, services, loans, leases, and sale of personal property.
Common Real-Life Scenarios
Scenario 1: You Paid for a Logo, But the Designer Only Sent PNG and JPEG Files
If the package listed only PNG and JPEG, you may not automatically be entitled to the AI, PSD, SVG, EPS, or Figma source file.
If the chat said “editable file included,” you have a stronger claim.
If the designer now asks for an additional source-file release fee, that may be valid if source files were not included. But if source files were promised, charging extra may be a breach.
Scenario 2: You Paid for a Website, But the Developer Will Not Give the Code
Ask first: what kind of website did you buy?
If you bought a custom-coded website, source code turnover may be strongly implied or expressly required. If you bought a hosted website service, your right may be limited to use of the hosted site. If the developer used licensed plugins, themes, or proprietary tools, they may not be allowed to transfer everything.
At minimum, a business client should insist on access to the domain, hosting, CMS admin, business emails, analytics, and data owned by the business.
Scenario 3: The Freelancer Says “I Own the Copyright”
The freelancer may be correct, especially for commissioned works where there is no written copyright assignment. But that does not automatically answer whether they must deliver source files. The source-file issue depends on the deliverables promised.
At the same time, the client may still have a practical or implied license to use the final output for the purpose for which it was commissioned.
Scenario 4: The Client Wants Raw Photos After Paying for Edited Photos
Unless RAW files were included, the photographer may refuse or charge extra. Edited photos are the final deliverables in many photography packages. RAW files may reveal the photographer’s workflow and may not represent the finished work.
Scenario 5: A Foreign Client Hired a Filipino Freelancer
Foreign clients dealing with Philippine-based freelancers should preserve written evidence. If documents from abroad will be used in Philippine proceedings, notarization and apostille may be needed depending on the document and forum. Electronic contracts and messages can still matter under RA 8792, but authentication becomes important.
If the Filipino freelancer is an individual residing in the Philippines and the foreign client has no Philippine residence, barangay conciliation may not be available or required. Enforcement may instead depend on the contract, chosen venue, platform dispute process, or Philippine court procedure.
Scenario 6: The Supplier Withholds Files Because the Client Has Not Fully Paid
A supplier may have a legitimate position if the agreement says source-file turnover happens only upon full payment. But the supplier should be careful not to withhold client-owned assets unrelated to the unpaid balance, such as domain names registered under the client, customer data, or accounts paid for by the client.
The safer solution is often staged release: payment of the undisputed balance, turnover of agreed files, and written reservation of disputed claims.
Contract Clauses That Prevent Source-File Disputes
The best time to solve this issue is before work starts.
A good creative or technical contract should answer these questions:
- What are the final deliverables?
- Are source files included?
- What file formats will be delivered?
- When will files be turned over?
- Is copyright assigned or only licensed?
- Can the client modify the work?
- Are third-party assets, fonts, plugins, stock media, and templates included?
- Who owns reusable tools, internal templates, presets, libraries, and pre-existing code?
- Who controls domain, hosting, repositories, and cloud accounts?
- What happens if the client does not fully pay?
- What happens if the supplier disappears or cannot continue?
- How will confidential information and personal data be handled?
Useful wording may look like this:
Upon full payment, the Service Provider shall deliver to the Client the final approved files and the following source files: [list exact formats/files]. The Service Provider assigns to the Client all economic rights in the commissioned work to the extent allowed by Philippine law, excluding the Service Provider’s pre-existing tools, templates, libraries, and materials identified in Annex A. The Client may edit, reproduce, adapt, publish, and use the work for its business purposes.
For software:
Upon full payment, the Developer shall turn over the complete source code repository, database schema, deployment instructions, environment variable list excluding secrets, documentation, and admin credentials for all Client-owned accounts. Third-party libraries remain subject to their respective licenses.
For design:
The package includes final PNG, JPEG, PDF, SVG, and Adobe Illustrator source files for the approved logo. Unused studies, rejected concepts, sketches, internal templates, and working drafts are excluded unless separately purchased.
Documents and Evidence To Prepare
| Document or evidence | Why it matters |
|---|---|
| Contract or signed proposal | Shows agreed deliverables and ownership terms |
| Quotation and invoice | Helps prove what package was paid for |
| Proof of payment | Shows full or partial performance by the client |
| Chat and email screenshots | Useful when no formal contract exists |
| Original electronic files or exports | Stronger than screenshots alone |
| Final delivered files | Shows what was already turned over |
| Demand letter | Shows formal request and deadline |
| Business registration or IDs | May be needed in court or agency filings |
| Barangay certification to file action | May be needed if barangay conciliation applies |
| Copyright registration or deposit certificate | Helpful evidence, though copyright exists from creation |
| Repository logs or access records | Useful in software disputes |
| Data-processing agreement | Important when files contain personal data |
Frequently Asked Questions
Can I demand the PSD, AI, Figma, or editable file after paying a designer?
Yes, if the editable file was included in the agreement. If the agreement only promised final files like PNG, JPEG, or PDF, you may request the editable file, but the designer may legally charge extra or refuse unless the facts show it was implied or promised.
Does paying for a logo mean I own the copyright in the Philippines?
Not always. For commissioned work by an independent contractor, Section 178.4 of RA 8293 says the commissioner owns the work, but copyright remains with the creator unless there is a written stipulation saying otherwise. A written copyright assignment is best.
Are source files the same as copyright?
No. Source files are the editable files or working materials. Copyright is the legal right to reproduce, adapt, distribute, display, and authorize use of the work. You can receive source files without owning copyright, and you can own copyright without physically receiving every internal working file, depending on the agreement.
Can a developer refuse to give source code after building my website or app?
It depends on the contract. If the developer was hired to build a custom website or app for turnover, refusing to release source code may be a breach. If the deal was for access to a hosted service or platform, the developer may not be required to give the underlying platform code.
Can I file a small claims case to force release of source files?
Small claims are mainly for money claims up to ₱1,000,000 under the Supreme Court’s expedited rules. If you want a refund or unpaid amount, small claims may help. If you want the court to compel delivery of source files or source code, you may need a different civil action such as specific performance and damages.
Do emails and Messenger chats count as proof?
They can. RA 8792 recognizes electronic documents and electronic data messages. The practical issue is authentication: you should preserve full message threads, email headers where possible, transaction records, payment confirmations, and original exports rather than relying only on cropped screenshots.
Can a freelancer charge extra for source files?
Yes, if source files were not included in the original package. Many creative professionals price source files separately because they allow future editing and reduce the client’s dependence on the original creator. But if source files were promised as part of the package, charging extra may be improper.
What if the source files contain fonts, plugins, stock assets, or templates?
The supplier may be unable to transfer third-party assets if the license does not allow it. A proper turnover should identify which parts are client-owned, which are licensed, and which require the client to buy a separate license.
Can I modify the work after receiving source files?
You may modify it if your contract, copyright assignment, or license allows modification. Even then, moral rights should be considered, especially if the creator’s name will remain attached to the modified work. Section 193 of RA 8293 gives authors rights related to attribution and objection to prejudicial distortion.
What should I do before paying the final balance?
Before final payment, confirm the turnover checklist in writing. For creative work, list exact file formats. For websites and apps, confirm repository access, admin credentials, hosting, domain, database, documentation, and third-party licenses. Pay through traceable channels and keep receipts.
Key Takeaways
- Paying for creative or technical work in the Philippines does not automatically give you source files.
- The strongest basis to demand source files is a clear written agreement, quotation, email, or chat message saying they are included.
- Under RA 8293, commissioned work and copyright ownership are not the same; copyright generally stays with the creator unless there is a written assignment.
- Source files, copyright, final deliverables, licenses, and moral rights are separate legal issues.
- Electronic contracts, emails, and chats can be important evidence under RA 8792.
- Small claims may help recover money, but compelling turnover of source files may require a different legal remedy.
- For websites, apps, and software, source code, credentials, repositories, databases, and documentation should be listed clearly before payment.
- The best protection is a written turnover clause that states exactly what files, rights, accounts, and access will be delivered upon payment.