Package & Share · Easy · 12 min

Share Your Game: Zip It, Upload to itch.io, and Beyond

Take your packaged Windows build, zip up exactly the right folder, and put it online — uploading to itch.io as a friendly first home for a hobby game, plus an honest look at what bigger storefronts involve.

LevelEasy Time~12 min EngineUE 5.4+ Hands-on14 checkpoints

Before this: Package Your Game for Windows: Make a Real .exe, Step by Step, Reduce Your Package Size and Fix Common Packaging Errors

By the end, you'll be able to
  • Identify exactly which folder and files your packaged build needs to run
  • Compress your build into a single, clean zip that other people can download
  • Create an itch.io project page and upload your game as a playable download
  • Understand, honestly, what moving to a bigger storefront later would involve

The last mile: getting your game into someone else's hands

You've packaged your project, so somewhere on your disk there's a folder with a .exe in it that actually runs your game. That's a huge milestone — but a folder on your own machine isn't something you can hand to a friend, post in a Discord, or put in your portfolio. To share it, you need to do two simple things: bundle the build into a single downloadable file (a zip), and host that file somewhere people can reach.

This lesson covers the friendliest possible path for a first hobby release: zip the build correctly, then upload it to itch.io — a popular, beginner-welcoming home for indie and hobby games where you can have a free download page online in minutes. We'll finish with a short, honest reality check on what 'bigger storefronts' actually involve, so you go in with clear expectations and no surprises.

A few words to lock in first

Tap a card to flip it

Before you upload

Tick these off so you're sharing something that actually works:

  • You have a packaged Windows build (a folder with your game's .exe inside it)
  • You double-clicked that .exe and the game ran — test it before anyone else does
  • You ideally moved the folder somewhere else (or to another PC) and confirmed it still runs from there
  • A free itch.io account (you can create one when you reach the upload step)

What to include — and what NOT to include

This is where most first-timers trip up, so let's be precise. When you package, Unreal creates a folder for your platform (for a Windows build this is usually a 'Windows' folder). Inside it you'll find your game's .exe alongside supporting folders — typically an 'Engine' folder and a folder named after your project that holds the cooked content. All of that together is the game.

The single most important rule: zip the folder that lets the game run as a self-contained unit, with the .exe and its sibling folders inside the zip. If you zip only the .exe by itself, it won't run on someone else's machine because all its data is missing.

Do NOT include your editor project. Files like the .uproject, the Content, Source, Config, Saved and Intermediate folders are your development project — they are large, may contain things you don't want public, and are not needed to play the game. Players only ever need the packaged output.

Zip your build and upload it to itch.io

Work top to bottom. Each row stays ticked even if you close the page and come back, so you can pick up where you left off.

  1. 1Find your packaged build folder

    Open the folder where you told Unreal to package the project. You're looking for the platform folder (for Windows, commonly a folder called 'Windows') that contains your game's .exe and its supporting folders.

    Open that folder and confirm the .exe is sitting in there next to the other folders. This whole folder is what you'll be zipping.

    TipIf you can't remember where you packaged it, re-run the package step and watch the output log — it prints the destination path when it finishes.

  2. 2Test the build by running it

    Double-click the .exe and play for a minute. Make sure it launches, the main menu (or first level) loads, and nothing obvious is broken.

    This is your last checkpoint before strangers download it. Catching a problem now is painless; catching it after twenty people have downloaded a broken build is not.

    TipBonus check: copy the build folder to a different drive or a friend's PC and run it there. That confirms the build is truly self-contained and not secretly leaning on files only your machine has.

  3. 3Zip the build folder

    In your file explorer, right-click the build folder and choose your operating system's 'compress' or 'send to zipped folder' option to create a single .zip file.

    Give the zip a clear, version-friendly name like 'MyGame-Win-v0_1.zip'. Including a version number now saves confusion later when you upload updates.

    TipOpen the finished zip and glance inside to confirm the .exe and its sibling folders are in there. A zip that's only a few kilobytes is a red flag that you zipped the wrong thing.

  4. 4Create a free itch.io account and start a new project

    Go to itch.io and sign up for a free account. Once signed in, look for the option to upload or create a new project (creators reach this from their dashboard / 'Upload new project' area).

    On the new project page, give your game a title and choose that you're uploading a downloadable game (as opposed to, say, a web game). Set the pricing to free, or 'name your own price', for a first hobby release.

    TipYou don't need everything perfect on day one — you can keep the page as a draft and only make it public when you're ready.

  5. 5Upload your zip and tag the platform

    In the project's files section, upload the .zip you made. itch.io lets you mark an uploaded file as being for a specific platform — mark it as a Windows download so players see the right button.

    Wait for the upload to finish completely before navigating away. Large builds can take a while depending on your connection.

    TipIf your zip is very large, revisit the 'reduce package size' lesson — a leaner build uploads faster and is friendlier for players to download.

  6. 6Add a description, screenshots, and instructions

    Write a short description of what the game is, add a couple of screenshots, and include plain instructions — for example, 'Download the zip, extract it, and run the .exe inside.' That extract-first step trips up players, so spell it out.

    Note the controls and mention it's a Windows build so Mac/Linux players aren't disappointed.

    TipA clear 'how to run it' line dramatically cuts the 'it won't open!' messages — many people forget they have to extract a zip before running anything.

  7. 7Save as draft, preview, then publish

    Save the page and use the preview to see it as a visitor would. Click through as if you were a player: does the download work, does the description make sense?

    When you're happy, set the page's visibility to public. Your game now has a real, shareable URL you can post anywhere.

    TipKeep the page as a draft while you're still tweaking — only flip it to public once you've previewed the download end to end.

A friend downloads your zip, double-clicks it, and says 'nothing happens.' What's the most likely innocent explanation — and what should you put on your page to prevent it?

itch.io now, or a bigger storefront later?

Free to create a page, beginner-friendly, and you can be live in minutes. There's no formal review gate to clear before a hobby build goes public, which makes it ideal for a first release, a portfolio piece, or sharing a work-in-progress.

It's also a genuinely good home for many indie and hobby games long-term — plenty of finished games live there happily. You don't have to 'graduate' off it.

QuizCheck yourself

1What should go inside the zip you share?

2Which of these should you NOT include when sharing your game?

3Why is itch.io a good first home for a hobby build?

ChallengeTry it yourself

Take your packaged Windows build all the way to a live (or draft) itch.io page. Zip the build with a versioned name, create the project, upload the zip and tag it as Windows, write a one-line 'how to run it' instruction, then use the preview to download and run your own game as if you were a stranger.

Hint 1

Zip the platform folder that contains the .exe — not just the .exe, and not your whole project.

Hint 2

Name the zip with a version, e.g. 'MyGame-Win-v0_1.zip', so future updates are easy to tell apart.

Hint 3

On itch.io, mark the uploaded file as a Windows download so players get the correct button.

Hint 4

Your 'how to run it' line should mention extracting the zip first, then running the .exe inside.

Finished the steps?

Mark this lesson complete

We'll remember it on your Academy page and unlock the next lesson below.

Questions beginners ask

Do players need Unreal Engine installed to run my game?

No. A packaged build is standalone — it ships with everything it needs to run, so players just download, extract and play. They never install the engine or your project. That's the whole point of packaging.

My zip is huge. Is that normal, and can I make it smaller?

A packaged build bundles the engine runtime and all your cooked content, so it's naturally larger than a typical app. If it feels excessive, the 'Reduce package size and fix common errors' lesson covers trimming unused content and other size wins before you upload.

Will my Windows build run on Mac or Linux?

No — a build is platform-specific. A Windows build runs on Windows PCs only. To reach Mac or Linux players you package separately for each of those platforms, which has its own setup. State clearly on your page that the download is for Windows.

Is itch.io free, and do I have to charge for my game?

Creating a page and hosting a free download costs you nothing to get started. You can set a game to free, 'name your own price', or a fixed price. For a first hobby release, free or 'name your own price' is a common, low-pressure choice.

Get the next lessons as they land

New Academy lessons, UE5 tips and tool releases — straight to your inbox. No spam, unsubscribe anytime.

Report a bug