[Game & Digital Content Licensing Deep Dive ④] Do Game Updates Require a New Rating in Korea? — Content Modification Reports, Reclassification, and New Rating Applications

Hello, I'm Jean Ji, a Certified Administrative Agent in Korea.

A game company is preparing a major update for the 15th of next month.

The update adds new characters and maps, changes some combat effects, and introduces a new payment feature.

The development team has nearly finished the patch.

The operations team has already prepared the user announcement and marketing schedule.

Just before release, however, the person responsible for compliance asks a question:

“If the game changes this much, do we need to obtain a new rating?”

This is where the issue becomes more complicated.

Not every update requires a new game rating.

At the same time, a game cannot automatically continue using its existing rating simply because the developer calls the change an “update.”

Korea's game content modification system also changed on October 9, 2025.

Certain minor changes that clearly do not affect the existing rating are now exempt from the modification reporting requirement.

For changes that remain subject to reporting, developers may generally report them before implementation or within 24 hours after the modification.

If the competent authority determines that the change is significant enough to require a different rating, it must notify the developer that the game is subject to reclassification within seven days of receiving the report.

This means that the correct question is not simply:

“Do we need another rating?”

A developer must distinguish between four different possibilities:

• Is the update exempt from reporting?
• Does it require a content modification report while allowing the existing rating to remain in place?
• Does it require reclassification?
• Or does the change go beyond a modification of the existing game and require a new rating application?

In this article, we will examine these four possibilities using a hypothetical game company, Company A, that is preparing a major update.

---

Game & Digital Content Licensing Deep Dive Series

1. Do game developers and publishers need separate business registrations?
2. When should you apply for a game rating in Korea?
3. Where should you apply for a game rating?
4. Do game updates require a new rating? — This article
5. What must be disclosed when a game includes probability-based items?
6. Who handles Korean regulatory procedures for games developed overseas?
7. What happens when the representative, address, or registered game business details change?
8. Is closing a game business as simple as canceling the business registration?
9. What happens to existing registrations when acquiring a game company or game business?

---

1. A Game Update Can Lead to Four Different Regulatory Outcomes

From a regulatory perspective, there is no single procedure that applies to every game update.

Under the current system, developers generally need to distinguish between four possible routes.

① Exemption from the Content Modification Report

If the change is clearly minor and does not affect the existing rating decision or required game-content information, a content modification report may not be required.

This is the simplest category.

However, whether a change qualifies depends on its actual effect on the game, not merely on how the development team labels the update.

② Content Modification Report While Maintaining the Existing Rating

Some changes must be reported but are not significant enough to require a different age rating.

In that case, the developer may complete the applicable content modification reporting procedure while maintaining the existing rating.

③ Reclassification

If a reported modification is significant enough to require a change in the game's rating, the game may become subject to reclassification.

Article 21(7) of Korea's Game Industry Promotion Act provides that, when a reported modification is considered substantial enough to require a different rating, the authority must notify the developer within seven days that the game is subject to reclassification.

The game must then go through a new rating process.

④ A New Rating Application Because the Change Exceeds the Scope of a Modification

Some changes may be too extensive to be treated as a modification of the existing game at all.

If the way the game is used changes substantially, or other factors make it difficult to regard the modified version as the same game for modification-report purposes, the report may be rejected and a new rating application may be required.

This means that the first task in a major update is not completing a reporting form.

The first task is comparing the version that originally received the rating with the version that will actually be released after the update.

---

2. Since October 2025, Certain Minor Updates May Be Exempt from Reporting

Older Korean guidance often states that any modification to a rated game must be reported within 24 hours.

That explanation is no longer sufficient by itself.

The Game Industry Promotion Act was amended in April 2025, and the new content modification rules took effect on October 9, 2025.

Under Article 21(5), a developer that modifies a rated game must generally report the modification before making the change or within 24 hours after the modification.

However, certain minor changes are excluded from this reporting requirement when it is clear that they do not affect the existing rating decision or required game-content information.

What can qualify as a minor change?

The amended Enforcement Rule identifies categories that may include:

• Correction of typographical errors
• Correction of translation errors
• Changes to screen or interface arrangements
• Changes to the way game information is displayed
• Fixes for errors that interfere with game progress
• Fixes for abnormal operation of particular functions
• Other matters specified by the Game Rating and Administration Committee

There is an important condition.

A change does not become exempt simply because it can be described using one of these labels.

It must also be clear that the modification does not affect the existing rating decision or required game-content information.

Consider a translation update.

Correcting a spelling mistake may qualify as a minor change.

But if a translation change introduces stronger sexual language, violent meaning, or other content relevant to the age rating, the analysis becomes different.

The same applies to screen changes.

Moving a menu button is not the same as adding a new sexualized image or violent visual element.

For regulatory purposes, the actual content of the change matters more than the size of the patch or the name given to the development task.

---

3. Some Games Must Still Report Changes Even When the Modification Appears Minor

There is another point developers must check before relying on the minor-change exemption.

Article 21(6) of the Game Industry Promotion Act identifies certain games for which modification reporting remains necessary despite the general exception for minor changes.

For example, games provided through youth game businesses or general game businesses may remain subject to reporting requirements for modifications other than changes to the exterior of the game device.

Certain games that simulate gambling-related activities defined under the Act may also be subject to separate treatment.

Therefore, developers should avoid broad assumptions such as:

“It is only a typo correction, so reporting is never required.”

or

“It only fixes a malfunction, so every type of game is automatically exempt.”

The analysis should proceed in two stages.

First:

What exactly changed?

Then:

Does the reporting exemption actually apply to this type of game?

Both questions matter.

---

4. Sometimes the First Question Is Whether the Updated Version Is Still the “Same Game”

Game companies routinely describe changes as updates, patches, expansions, or version upgrades.

But a developer's internal label does not automatically determine how the game will be treated under Korean rating rules.

In some situations, the more fundamental question is whether the modified game can still be treated as a modification of the originally rated game.

A Korean Supreme Court decision illustrates why this matters.

A Free Mobile Game Converted into a Paid Arcade Game — Supreme Court Decision 2021Do4785

The case involved a game that had originally received a rating as a free mobile game.

It was later provided in the form of an arcade-style machine installed at a PC gaming venue.

Users inserted KRW 10,000 in cash and were allowed to play for three minutes.

The underlying game content still had a connection to the original mobile version.

However, the way users accessed and paid for the game had changed substantially.

The Supreme Court held that the analysis should not focus only on the internal content of the game.

The Court also considered the operating method that was closely connected to how the game content was implemented.

Providing the game under operating conditions different from those described in the original rating application or game content description could constitute providing a game different from the version that had received the rating.

The Supreme Court therefore reversed and remanded the lower court's judgment.

Source: Supreme Court of Korea, July 21, 2021, Decision 2021Do4785

The point of this case is not that every change to a payment model automatically requires a new rating.

The decision involved a specific and substantial change in operating structure.

Its practical significance is narrower but important:

Even when the title and graphics remain similar, major changes to how users access, pay for, or operate the game can affect whether the existing rating remains applicable.

Developers should therefore examine updates more carefully when they involve situations such as:

• A free game becoming a paid-use service
• Major changes to the purchase, use, or transfer of in-game currency
• Changes in platform together with changes in how the game is used
• Significant changes to account continuity or user game data
• A new operating structure that differs substantially from the version originally rated

In these situations, the issue may go beyond a simple modification report.

The developer may need to determine whether the change requires a modification report, reclassification, or an entirely new rating application.

---

5. Does Every Update Lead to Reclassification? — What the “3,000 Reports and 5%” Figure Actually Means

How often did content modification reports historically lead to additional rating action?

In October 2024, the Game Rating and Administration Committee announced measures to simplify documentation for content modification reports.

At that time, approximately 3,000 content modification reports were being received and processed each year.

The Committee also stated that decisions such as reclassification were made in approximately 5% of those cases.

This tells us one useful thing:

Most reported updates at that time did not result in decisions such as reclassification.

But the figure should not be used as a prediction for a particular game.

It was a 2024 statistic.

The regulatory system later changed.

2024 Introduced Document Simplification; 2025 Introduced Reporting Exemptions

These two reforms are different.

The 2024 measure reduced the amount of documentation required for certain minor content modification reports.

The developer still had to make the report.

The later 2025 reform went further.

Certain minor changes became exempt from the content modification reporting requirement itself.

Submitting fewer documents is not the same as being exempt from reporting altogether.

For that reason, the approximately 3,000 annual reports and 5% figure from 2024 should not be presented as the current number of reports or current reclassification rate in 2026.

The practical lesson is not that a particular update has a “5% chance” of being reclassified.

The correct question is whether the specific update:

• Qualifies for the reporting exemption
• Requires a content modification report
• Affects the existing rating
• Or exceeds the scope of a modification of the existing game

The actual content of the update must be examined first.

---

6. When Must a Content Modification Report Be Filed? — The 24-Hour and 7-Day Rules Mean Different Things

Return to Company A.

The company plans to release its major update on October 15.

Assume that the update is subject to the content modification reporting requirement.

When should the report be filed?

Under Article 21(5) of the Game Industry Promotion Act, the developer may generally:

• Report the modification before making the change; or
• Report it within 24 hours after the modification

This creates an important compliance option.

However, it can also create a misunderstanding.

A developer may think:

“If we have 24 hours to report it, we can release the update first and deal with the paperwork tomorrow.”

That interpretation goes too far.

The 24-hour period concerns the reporting deadline.

It does not guarantee that the modified game remains appropriate for the existing age rating.

Imagine a game currently rated for users aged 15 and above.

The developer adds much more intense violent content.

Even if the company submits its report within 24 hours after release, the question of whether the existing rating remains appropriate still has to be considered.

For updates that may significantly affect the rating, filing the report in advance may allow the developer to incorporate the regulatory outcome into the release schedule.

A Pre-Modification Report Does Not End the Process

If the developer reports the modification before implementation, additional action may still be required after the update actually goes live.

Article 21(8) of the Game Industry Promotion Act requires a developer that filed a pre-modification report to submit information concerning the actual modified version so that the authority can verify whether the final implementation matches the reported changes.

The Enforcement Rule requires this information to be submitted within 24 hours after the actual modification.

The Game Content Rating Board also introduced a pre-modification reporting function in June 2026.

Under its guidance, when a developer receives a decision allowing the existing rating to remain in place and then implements the modification, a follow-up implementation report must be submitted within 24 hours after the game is modified.

Consider an example.

The developer reports in advance that the update will add only one new character.

The final build, however, also introduces a payment function and stronger combat effects.

The fact that a pre-modification report was filed does not automatically mean that every change in the final build has been covered.

The company must compare the reported plan with the version that was actually released.

A pre-modification reporting workflow should therefore be managed as one continuous process:

Pre-modification report → review result → actual update → follow-up submission within 24 hours

What Does the Seven-Day Period Mean?

Article 21(7) provides that, when the authority determines that a reported change is significant enough to require a different rating, it must notify the developer within seven days that the game is subject to reclassification.

This seven-day period is often misunderstood.

It does not mean that the game will receive its new age rating within seven days.

The seven days refer to the deadline for notifying the developer that reclassification is required.

The subsequent rating procedure is separate.

If Company A plans an October 15 update and receives a reclassification notice, it must account for the additional rating procedure in its release schedule.

The company cannot bypass the process simply because the update date has already been announced to users or because marketing expenses have already been committed.

For major updates, the practical release date should therefore reflect not only technical completion but also the regulatory procedures that may still be required.

---

7. What If the Content Modification Report Is Rejected?

Assume Company A correctly identifies the update as something that should be reported.

It files the content modification report.

The report is rejected.

What should the company do next?

The first response should not be to slightly rewrite the same form and submit it again.

The company should first determine why the report was rejected.

The Enforcement Rule of the Game Industry Promotion Act distinguishes between several different outcomes for content modification reports.

A reported update may allow the existing rating to remain in place.

It may require reclassification.

In some cases, however, the modification may exceed the scope of what can be processed as a modification of the existing game.

For example, if the way the game is used changes substantially or continuity of game account information is not maintained, the modification report may be rejected and the developer may need to submit a new rating application.

This creates an important distinction.

Reclassification

The game is still being treated as a modification of the existing game, but the change is significant enough to require a new rating process.

Modification Report Rejection

The change is considered too extensive to be handled through the existing game's content modification procedure.

A new rating application may therefore be required.

Both situations can ultimately lead to a new rating process.

But the legal and procedural reasons are different.

If a modification report is rejected, the developer should therefore examine:

• How substantially the method of using the game has changed
• Whether existing user accounts and game data continue to carry over
• How the current service structure differs from the game content description originally submitted
• Whether the problem is simply missing documentation
• Or whether the developer has chosen the wrong regulatory procedure altogether

Repeating the same application without understanding the reason for rejection may simply reproduce the same problem.

---

8. How Should a Development and Operations Team Manage a Major Update in Practice?

Now return to Company A's October 15 update.

The update includes:

• New characters
• New maps
• Modified combat effects
• Corrections to typos
• Fixes for gameplay errors
• A new payment function

If the company treats all of these changes as a single “update,” it may overlook important regulatory distinctions.

A more practical approach is to work through the update in four steps.

Step 1. Separate the Changes by Type

Start by breaking the update into individual changes.

Typographical and translation corrections should be examined to determine whether they qualify as minor changes exempt from reporting.

Gameplay error fixes should also be reviewed against the relevant minor-change provisions.

New characters and combat effects should be reviewed to determine whether they introduce content that could affect the existing age rating.

The payment function should be examined in terms of:

• How users pay
• What they receive
• How in-game currency or items are used
• Whether assets can be transferred
• Whether the actual way the game is played has changed

After examining each change separately, the developer should review the final update as a whole.

Several small changes may collectively make the final version significantly different from the version that originally received the rating.

Step 2. Prepare a Before-and-After Comparison, Not Just Patch Notes

Patch notes are generally written for players.

They explain what has been added or fixed.

For regulatory review, a more detailed comparison may be necessary.

Useful materials can include:

• The original rating decision
• The original game content description
• Screenshots or gameplay footage before and after the update
• Detailed descriptions of new features
• The structure of payments, items, and in-game currency
• The actual release build
• The scheduled update date

Suppose the patch notes simply state:

“New store feature added.”

That may not be enough to understand the regulatory significance.

A more useful explanation would identify:

• What users pay
• What they receive
• Whether the purchased item or currency affects gameplay
• How it can be used
• Whether it can be transferred
• Whether the payment structure changes how users participate in the game

These materials are useful not only for determining whether a report is required.

They may also help with pre-modification reporting, requests for supplementary information, and later verification that the live version remains consistent with the rating.

Step 3. Confirm Which Authority Handles the Follow-Up Procedure

The authority responsible for the original rating may not necessarily handle every later procedure.

Responsibility can depend on the type of game, age rating, distribution method, delegated authority, and whether the game was rated through a designated self-rating operator.

Developers should therefore confirm:

• How the original rating was obtained
• Whether responsibility for follow-up procedures has been transferred
• Which authority currently handles the modification report
• Whether a designated self-rating operator has authority over the relevant follow-up procedure

The Game Content Rating Board introduced a self-check function for content modification reports in March 2026.

The function allows company representatives to review whether a modification appears to require reporting before proceeding to the application page.

This can be useful as an initial compliance tool.

But the result depends on the information entered.

If the developer omits a new payment feature or fails to accurately describe changed content, completing the self-check does not resolve the legal issue by itself.

The quality of the underlying information remains critical.

Step 4. Build the Regulatory Outcome into the Update Schedule

Company A has already selected October 15 as its target release date.

But whether the game can actually be released on that date depends on the nature of the changes.

If the update appears exempt from reporting, the company should still document the basis for that conclusion.

If reporting is required, the company should decide whether to use:

• A pre-modification report; or
• A report within 24 hours after implementation

If the company chooses advance reporting, it must also schedule the post-implementation submission.

If reclassification is reasonably possible, the company should allow time for the additional rating process.

If the changes may exceed the scope of a modification of the existing game, the company may need to reconsider the schedule on the assumption that a new rating application could be required.

This changes the way an update schedule should be managed.

The most important date is not necessarily the day the patch file is technically complete.

It is the date on which the company is actually ready to distribute the updated game in compliance with the applicable Korean procedures.

---

When Can a Developer Handle the Update Internally, and When Is Professional Review Useful?

A developer may be able to review a straightforward update internally when the changes are clearly minor and do not affect the existing rating.

Examples may include simple typographical corrections, translation errors, or technical fixes where the effect on the rated content is clearly limited.

Official self-check tools and guidance from the relevant rating authority may also help the developer determine whether a content modification report is likely to be required.

The analysis becomes more complicated when the update involves:

• New characters or content with a different level of violence or sexual expression
• Changes to payment systems
• Changes to in-game currency or item usage
• Significant changes to the way users access or play the game
• Platform changes
• Changes to the service structure
• Uncertainty over whether the existing rating can remain in effect
• A fixed update date that may be affected by reclassification or a new rating application

In these situations, the central task is not simply preparing a form.

The existing rating materials and the actual update must be compared to determine which regulatory route applies.

Within the lawful scope of administrative practice in Korea, a Certified Administrative Agent may assist with reviewing the existing rating documents, identifying the relevant administrative procedure, organizing supporting materials, and preparing for the applicable filing process.

Professional review does not guarantee that the existing rating will remain unchanged or that a particular rating outcome will be issued.

Its practical purpose is to identify the correct procedure before the update schedule is disrupted by an unexpected reporting, reclassification, or new application requirement.

---

Conclusion: Not Every Game Update Requires a New Rating

Return to Company A's original question:

“Do we need a new rating every time we update the game?”

No.

Not every update requires a new rating.

But that does not mean every update can automatically continue under the existing rating.

Under the current Korean system, the developer must distinguish between several possible outcomes.

If the change is clearly minor and meets the statutory requirements for exemption, the developer should determine whether the modification report can be omitted.

If reporting is required but the existing age rating remains appropriate, the game may proceed through the content modification reporting process while maintaining its existing rating.

If the modification is significant enough to require a different rating, the game may become subject to reclassification.

If the update exceeds the scope of a modification of the existing game, the developer may need to consider a new rating application rather than relying on the content modification procedure.

Developers must also distinguish between:

• Reporting before the modification
• Reporting within 24 hours after the modification
• Follow-up submission after a pre-modification report
• The seven-day notification period for reclassification

The seven-day period does not mean that a new rating will automatically be completed within seven days.

Ultimately, the most important question is not the size of the patch or the number of new characters.

The key question is how the game that users will receive after the update differs from the version that originally obtained the rating.

If you are preparing a game update in Korea and it is unclear whether the changes qualify for a reporting exemption, require a content modification report, trigger reclassification, or require a new rating application, you can request a free initial review based on the existing rating materials and the actual planned changes.