Start Building

By Lesson 12 you have optimized your UEFN experience for performance and platform constraints. The next step is packaging it for Fortnite, publishing so it goes live, and discovery so players can find it.

In this lesson you will:

  • Package your UEFN project for Fortnite and run a pre-publish checklist.
  • Set island details and metadata (name, description, tags, images) that affect discovery.
  • Apply discovery best practices so your experience appears where players look.

1. Why Packaging and Metadata Matter

When you publish from UEFN:

  • Your experience becomes an island (or map) inside Fortnite Creative 2.0.
  • Island details (name, description, thumbnail, tags) are what players see in the Discover tab and in search.
  • Packaging is the process of building and uploading the experience so Fortnite can run it. If something is misconfigured, the build can fail or the experience may not show up correctly.

Spending a little time on clear naming, accurate tags, and a good thumbnail pays off in discovery and first impressions.

2. Pre-Publish Checklist

Before you hit Publish, run through this list:

  • [ ] Performance and constraints – You have done at least one pass from Lesson 12 (no overloaded areas, event-driven logic where it matters, tested on real devices if possible).
  • [ ] Core loop works – Spawns, objectives, win/lose conditions, and respawn flow work as intended in a full playthrough.
  • [ ] No placeholder or broken content – Replace or remove debug text, test devices, and obvious placeholders.
  • [ ] Island name and description – Decide on a short, clear name and a description that explains what the experience is and why it is fun (see below).
  • [ ] Thumbnail and optional gallery images – Prepare at least one image that represents your experience (in-game screenshot or edited key art). Follow Epic’s current specs (resolution, aspect ratio) for Creative islands.

If you use Verse or custom devices, do a final test in Fortnite (not only in UEFN editor) to confirm everything runs in the live environment.

3. Setting Island Details and Metadata

In UEFN, island details (or project settings, depending on the current UI) are where you set:

  • Island name – Short and memorable. Avoid vague names like “My Map.” Include the type of experience if it helps (e.g. “Tower Defense – Waves,” “Obby – Neon Run”).
  • Description – One or two sentences that say what the experience is and what makes it fun. Include key hooks: game mode, number of players, difficulty, or unique twist. This text often appears in Discover and on the island’s info panel.
  • Tags / categories – Use the tags Epic provides (e.g. by genre, mood, or feature). Choose tags that match how players search (e.g. “Obby,” “PvP,” “Horror,” “Co-op”). Do not over-tag or use irrelevant tags; that can hurt trust and discovery.
  • Thumbnail – The main image shown in Discover and in search results. Use a clear, readable image (key moment, arena, or logo). Follow Epic’s recommended size and format so it does not get cropped or distorted.
  • Gallery (if available) – Additional screenshots or art that show gameplay or atmosphere. Helps players decide to try your experience.

Pro tip: Look at popular islands in Discover in your genre. Note how their names, descriptions, and thumbnails are written and formatted. Use that as inspiration without copying.

4. Packaging Your Experience

Packaging is the step where UEFN builds your project into a format Fortnite can run:

  1. In UEFN, use the Publish or Package flow (exact menu name may vary by version). This usually builds the level, Verse code (if any), and assets.
  2. Resolve any errors reported during the build (missing references, Verse compile errors, or validation failures). Fix them and try again.
  3. Once the build succeeds, you typically upload to Epic’s servers and then submit for publishing (or similar) so the island is available in Fortnite.

Common issues:

  • Verse errors – Fix any compile or runtime errors reported in the output. A single Verse error can block packaging.
  • Missing or invalid assets – Replace or remove references to assets that are missing or not allowed in Creative.
  • Naming or path issues – Avoid special characters or very long names in key assets or the project if the packager is strict.

After a successful publish, your experience should appear in your Creator dashboard and, once approved (if applicable), in Fortnite under your island or in Discover.

5. How Discovery Works (High Level)

Fortnite’s Discover tab surfaces islands based on:

  • Relevance – Tags, name, and description matching what players search or browse.
  • Engagement and quality – Playtime, retention, and ratings (where applicable) can influence placement over time.
  • Freshness and updates – New or recently updated experiences are often highlighted.

You do not control the algorithm directly, but you can control:

  • Accuracy of name, description, and tags.
  • Quality of thumbnail and gallery so players click and try your experience.
  • Stability and performance so players stay and rate fairly (Lessons 11 and 12).

6. Discovery Best Practices

  • Name – Clear, memorable, and aligned with the experience. Include the type of game (e.g. Obby, PvP, Horror) if it helps.
  • Description – What is it, who is it for, what makes it fun? Keep it concise; many players skim.
  • Tags – Use all relevant tags Epic offers. Match how your audience searches (e.g. “2–16 players,” “Co-op,” “Competitive”).
  • Thumbnail – One strong image that represents the experience. Avoid cluttered or dark images that are hard to read at small size.
  • Updates – When you fix bugs or add content, republish and (if the UI allows) note “Updated” or similar so returning players know something changed.

Avoid:

  • Misleading names or thumbnails – They can lead to bad first sessions and poor ratings.
  • Tag stuffing – Using every tag when only a few apply can look spammy and hurt trust.

7. After Publishing – What to Do Next

Once your experience is live:

  • Play it yourself in Fortnite (as a player) to see exactly what others see in Discover and in-session.
  • Share the link (if Epic provides one) with friends or communities to get early feedback and some initial plays.
  • Monitor any creator dashboard metrics (plays, retention, ratings) and use them to decide what to fix or improve in the next update.

In Lesson 14 we will look at creator economy and monetization in UEFN and Fortnite Creative 2.0 – how you can earn from your published experience and what options exist for creators.

8. Recap

You now have:

  • A pre-publish checklist so your experience is ready for packaging and release.
  • A process for setting island details (name, description, tags, thumbnail) that support discovery.
  • An understanding of packaging and how to fix common build issues.
  • Discovery best practices so your experience is findable and accurately represented.

For the latest steps and UI, always check Epic’s UEFN and Fortnite Creative documentation and the in-editor Publish flow.