My Fortnite Creative Map Was Stolen — What to Do Right Now

You built the map. You put in the hours. Now someone else has published it under their name and is collecting the plays. Here is exactly what to do — from documenting your authorship to reporting to Epic to escalating if they don't act.

Part of the Fortnite & UEFN Creator Safety guide.

First: Confirm It's Actually Theft, Not Coincidence

Before you report anything or send any messages, take twenty minutes to verify what you're dealing with. Fortnite Creative has tens of thousands of published maps, and some design patterns — zone wars, deathrun obstacles, certain game modes — appear across many creators independently. Coincidental similarity is real and common.

Actual map theft looks different. The stolen version will share structural layouts you designed, specific Verse mechanics or code patterns you wrote, distinctive decorative choices that couldn't realistically be recreated independently, or entire map sections reproduced with only minor surface changes. If you're seeing one generic game mechanic in common, that's probably convergent design. If you're seeing your exact prop placement, your specific code structure, and the same unusual design decisions you made — that's theft.

Document this evaluation. Write down specifically what was taken, not just "it looks like mine." The more concrete you can be — "the northeast section's obstacle layout matches mine in this exact sequence" — the stronger your report will be.

Step 1: Gather Your Evidence Before You Do Anything Else

Evidence is everything in an IP dispute. Accounts get deleted. Messages disappear. Screenshots get lost. Before you contact anyone, build your evidence package.

UEFN Version History

UEFN (Unreal Editor for Fortnite) maintains a version history tied to your Epic account. Open UEFN, navigate to your project, and export or screenshot your complete version history — it shows your Epic account ID, every saved version with timestamps, and the project UUID. This is strong first-party evidence because it comes directly from Epic's own system and cannot be faked by someone claiming ownership after the fact.

External Version Control

If you used git or any external version control for your project files, your commit history is timestamped and cryptographically signed. Export your git log. Even if you only pushed to a private repository, the local commit timestamps establish a clear creation timeline. This is particularly valuable for Verse code, where git diff can show exactly what you wrote and when.

Development Screenshots and Video

Most creators take progress screenshots or record development streams. Pull together everything you have — early-stage screenshots showing work in progress, stream recordings, preview videos you posted in your community Discord. These have metadata timestamps. Even your photo library's screenshot dates are useful supporting evidence.

If you livestreamed any development, VODs on Twitch or YouTube are excellent evidence because they're timestamped by the platform and show real-time creation.

Discord and Social Announcements

Find any Discord messages, tweets, TikToks, or forum posts where you announced the map, shared a preview, or discussed it — especially anything predating the stolen version's publish date. A Discord message from three months ago saying "just finished the final section of my deathrun" with an image is solid evidence. Export or screenshot these with the dates visible.

VerifyUGC Map Registry

If you've registered your map on VerifyUGC's verified map registry, your registration timestamp is recorded against your Epic account and the island code. This is designed specifically as prior-art documentation — it exists to be cited in exactly this kind of dispute. Pull your registration certificate from your VerifyUGC profile.

If you haven't registered yet, do it now for your current and future maps. It takes a few minutes and creates a timestamped public record that predates any future theft claim.

Step 2: Document the Stolen Version

Simultaneously, document everything about the infringing map while it's still up. Screenshots of the island listing, the island code, the publishing account's name, the publish date (visible on island details pages), and side-by-side comparisons of matching elements between your map and theirs.

Record video of the stolen map being played if possible. It's harder to claim "it's different" when you have direct footage showing the same layout, the same mechanics, the same section structure.

Note the exact island code of the stolen map. You'll need it for every report you file.

Step 3: Understand What Counts as Map Theft vs. Inspiration

This matters because Epic's review process, and any potential legal avenue, will evaluate the same question. The distinction is important.

Theft means someone took your actual work — your project files, your Verse scripts, your map structure — and republished it as their own. This is a clear intellectual property violation.

Copying (a gray area) means someone played your map extensively and reproduced it closely from memory or observation, without having your actual files. Courts and platform policies treat this differently than direct file theft, but it's still often actionable if the similarity is substantial enough.

Inspiration means someone made a similar type of map, used the same genre conventions, or built something with a superficially similar theme. This is not theft. A "box fight with circular rooms" is not protectable. Your specific box fight layout with your specific prop arrangement and your specific Verse scoring logic is.

When you report to Epic, be precise. Don't claim theft if what happened is heavy inspiration — it weakens your credibility. If what happened is clear file copying or structural reproduction, say so specifically and with evidence.

Step 4: Report to Epic Games

Epic has a content reporting pathway for Fortnite Creative and UEFN. This is your official channel and it should be your first escalation step.

What to Submit

Use Epic's support portal to file a content dispute report. Your submission should include:

• Your Epic account username and the island code of your original map
• The island code of the infringing map and the account name of the publisher
• A clear, factual description of what was taken — specific sections, code, layouts
• Your evidence package: UEFN version history export, development screenshots with dates, Discord announcements, git log if applicable, VerifyUGC registry certificate
• Side-by-side comparison screenshots showing the matching elements

Be professional and factual in your submission. Emotional language ("they stole my life's work!") doesn't strengthen a report. Specific, documented claims do. Focus on what you can prove, not how you feel about it.

What to Expect from Epic

Epic's review process is not fast. Expect days to weeks for a response on most cases. They will evaluate your evidence and the infringing map. If they find in your favor, they can unpublish or remove the island. In clear-cut cases with strong evidence, this is the expected outcome. In ambiguous cases, they may take no action.

You will not necessarily receive detailed feedback on their decision. This is frustrating but standard — large platforms cannot litigate every content dispute in detail. If Epic doesn't act and you believe the theft is significant, you have further options.

Step 5: Direct Contact and Community Pressure

While your Epic report is pending, you have other avenues.

Contact the Other Creator Directly

This seems counterintuitive but it sometimes works, especially when the theft was opportunistic rather than malicious — someone who grabbed a file from a leaked source without fully thinking through the consequences. A direct, calm message that says "I built this map, here is my evidence, please take it down or credit me appropriately" gives them a chance to resolve it without escalation. Keep a record of this contact and their response (or non-response) — it's part of your evidence trail.

Don't threaten legal action in your initial message unless you're actually prepared to pursue it. Empty threats erode your credibility.

Community Reporting via VerifyUGC

Add the infringing creator to VerifyUGC's blacklist with documentation of the theft. This serves multiple purposes: it warns other creators who might collaborate with them, it creates a public record of the incident, and it signals to the broader UEFN creator community that this person operates dishonestly. The VerifyUGC Discord bot lets your community members add the flag to their own servers with a single command.

Step 6: Escalation — Cease-and-Desist for Serious Cases

If Epic doesn't act and the theft is significant — the stolen map is generating real engagement payout under Epic's creator economy, or the thief is monetizing it through sponsorships — a cease-and-desist letter is your next escalation step.

A cease-and-desist is a formal legal letter, typically from an attorney, demanding that the infringer stop the infringing activity. It is not a lawsuit — it's a notice that you're aware of your rights and will pursue them if the activity doesn't stop. For most opportunistic infringers, a letter from an attorney is sufficient to prompt takedown and apology.

For a C&D to be effective, you need:

• The infringer's real identity (sometimes discoverable through their social accounts or public Epic account information)
• Clear evidence of original ownership (everything you've already gathered)
• An attorney willing to send the letter (many IP attorneys offer flat-fee C&D services)

The cost of a cease-and-desist letter is modest relative to the seriousness of protecting your creative work. If the theft is significant and Epic hasn't acted, this is worth considering.

Building Protection Going Forward

The hardest lesson from map theft is that documentation needs to happen before the theft, not after. A registration in the VerifyUGC map registry made after you discovered the stolen version is less useful than one made during development.

Build these habits for every new project:

• Register your island in the VerifyUGC map registry as soon as you have a publishable version — even before you go public
• Keep UEFN's version history intact; don't delete old versions
• Use git for Verse code; push to a private remote regularly
• Post development updates in your Discord or social channels; these timestamps are evidence
• Screen collaborators through VerifyUGC before sharing island access
• Set collaborator permissions in UEFN to the minimum necessary for the work being done

Most map theft is opportunistic. Creators who demonstrate they have documentation and know their rights are significantly less likely to be targeted — and far better positioned to respond when something does happen. Want the full playbook? Take our free creator safety course.