Set up an operating business
Assess the investor’s market-access route, the proposed Vietnam applicant and its ability to carry the operational responsibilities. Ownership conditions need investor- and treaty-specific review.
Legal Advice for Video Game Development, Publishing & Operations in Vietnam
For overseas studios, publishers and investors developing games, planning a Vietnam release or reviewing a live title. Connect the operating structure, publishing rights, classification, licensing, player data and contracts before agreeing a launch or expansion plan.
Choose who will publish and operate in Vietnam
Work with a local publisher
Clarify who holds the rights, applies for the relevant approvals, operates the service and handles players, payments and data. A publishing agreement should match the actual allocation of work.
Acquire or invest in an operator
Review the company, existing titles, rights, approvals, contracts and liabilities. Identify the effect of the proposed ownership or operating changes before agreeing the transaction.
Screen the interaction model before selecting a procedure
The G1–G4 framework distinguishes how players interact with each other and with the enterprise’s game servers. A genre label or app-store description is not enough; use a demo and architecture diagram.
| Initial category | Interaction pattern to examine |
|---|---|
| G1 | Multiple players interacting with one another through the enterprise’s game servers. |
| G2 | Player-to-enterprise-server interaction; check whether any player-to-player feature changes the classification. |
| G3 | Players interacting with one another without interaction with the enterprise’s game servers. |
| G4 | Network-downloaded games without interaction between players or with the enterprise’s game servers. |
Provider-level requirements and title-level requirements must be considered separately. G1 and G2–G4 follow different routes; confirm the current procedure for the actual model. For G1 document preparation, use the dedicated service page.
Agree the publishing rights and operating responsibilities
Before launch commitments, review the territory, platforms, exclusivity, term and scope of the rights granted. Confirm the rights holder’s authority and rights to localisation, updates, artwork, music and marketing materials.
- Set revenue-sharing, reporting, audit and payment arrangements with clear reconciliation rules.
- Allocate responsibility for regulatory submissions, content changes, player support and incident response.
- Address data access, migration, continuity and the handling of players if the relationship ends.
- Align termination and renewal terms with the rights and approvals needed to continue operating.
Turn the launch plan into an evidence checklist
| Workstream | Evidence to assemble | Question before launch |
|---|---|---|
| Rights & content | Rights documents, playable build, content description and proposed localisation. | Do the rights and reviewed content cover the intended release? |
| Player safeguards | Age assessment, player-information controls and relevant usage controls. | Can the operating team demonstrate the controls required for this title? |
| Systems & payments | Architecture, hosting and domain information, payment flows and vendor responsibilities. | Do the described arrangements match the system that will operate? |
| Data & support | Data map, player terms, privacy information and incident/support responsibilities. | Who handles player requests, security issues and personal data? |
| Regulatory readiness | Applicable provider- and title-level records, outstanding requests and conditions. | Which unresolved items prevent the proposed launch? |
Plan for updates and the life of the title
Keep a record of changes to content, systems, publishing partners, rights and the operating business. Assess their effect before implementation rather than assuming an initial approval covers every later release. Include renewals and continuity planning in the operating calendar.
The procedural framework must be read with the 2026 amendments and any applicable temporary measures. This overview does not prescribe a universal filing authority, processing time or foreign-ownership percentage.
Connect development rights with publishing and live operations
Development and co-development
Trace employee and contractor rights to the code, art, music and updates. Agree background IP, third-party components, acceptance and the rights to localise or hand over the product.
Player data and service partners
Map player accounts, analytics, software development kits (SDKs), hosting and payment partners. Review data roles and operating commitments alongside the publishing and vendor contracts.
Software and subscription activities
If the studio also supplies development services or hosted software, connect the game project with the separate code-ownership, contract and SaaS delivery questions.
Explore the wider business context
If the project also involves a marketplace, security service or other business activity, explore legal advice by industry and business model before extending the game review to those activities.
What the initial review can resolve
Send a non-confidential demo summary, interaction model, investor and publisher structure, rights position and target launch window. The agreed review can identify the likely classification, route questions, missing evidence and responsibilities before detailed filing work begins.
Legal work, engineering changes, localisation, commercial negotiations and authority processing are separate parts of the schedule. A filing-period estimate is not a commitment to a launch date. Fees and deliverables are agreed after the relevant workstreams are identified.
Questions before you proceed
Can an overseas studio use a local publisher instead of setting up its own operation?
Assess the proposed publishing structure and responsibilities. Review the partner, rights agreement and actual operating arrangements; a contract alone does not establish that every regulatory requirement has been met.
Are all multiplayer games G1?
Review the interaction model and server arrangements. G1 and G3 differ in the role of the enterprise’s servers; use technical evidence rather than the multiplayer label alone.
Does the provider’s licence cover every new title?
Provider-level and title-level requirements are distinct. Identify the route for the specific category and title before scheduling release.
Can we use one foreign-ownership percentage for every investor?
No. Assess nationality, applicable market-access commitments and the proposed structure. Do not apply a headline percentage without checking the investor’s position.
Can we promise a launch date when the application is filed?
Only after considering the complete readiness picture. Requests for further information, rights gaps, technical changes and content work can affect the timetable.
Sources & scope
The applicable route depends on the activity, investor, location and current rules at the time of implementation. Detailed filing requirements are addressed in the linked procedure guides.