# Is Unreal Engine bad for Small Games? — retained record

> Retained reddit record from reddit:gamedev.

Canonical: https://highsignal.app/data/records/ef19d6d7f843ab4a

[← sources](https://highsignal.app/data)


source: [reddit](https://highsignal.app/data/reddit) (reddit:gamedev)  published 2026-10-21 03:33 ingested 2026-10-22 02:38

[original source ↗](https://www.reddit.com/r/gamedev/comments/1xbckp9/is_unreal_engine_bad_for_small_games/)

## retained text



```
I’m currently studying game art in college, and I’m required to use Unreal Engine throughout my course, even for personal projects I make in my free time.

After staring at the same 3D grid stretching into the distance beneath a passable skybox every time I open a new project, it got me thinking.

I constantly hear the same advice given to aspiring game developers: **Make tiny games. Finish them. Move on. Repeat.**

And I understand the value of that advice. Small games let you experience the entire development process, practice scoping, make decisions under constraints, and actually finish something. When you make a mistake, it’s cheap. You get to see how everything comes together instead of spending years working on individual systems for a game that might never be completed.

I can absolutely see the value in that, especially for beginners.

But something about that advice has always bothered me.

The game I’m currently making for my college course is technically a small game, too. It’s not some massive open-world RPG or an overly ambitious dream project. It’s a single-level exploration game with no button interactions. It’s a relatively contained experience with a manageable scope.

The difference is that we’re expected to develop it to a much higher standard than what people on the internet usually mean when they recommend making small games. It’s also intermittent, like everything in college. 

It has to be polished, reasonably intricate, and developed with industry-level expectations in mind. That means thinking about the quality of the art, the consistency of the experience, the production process, and all the little details that separate a functioning prototype from something that feels professionally made.

And honestly, I think I’ve learned more from that process than I ever would have from making tiny game after tiny game on my own.

It’s made me question what exactly makes small games such an effective learning tool. Is it their size? The fact that you finish them? Or simply that you’re constantly encountering problems and figuring out how to solve them?

Because to me, **the value of a project isn’t necessarily determined by its size, how long it takes, or even whether you finish it. It’s determined by what you learn while making it.**

I genuinely think there’s a lot of value in failing at an ambitious project. Potentially even more than succeeding at several tiny ones, depending on what you’re trying to learn.

A failed project that forces you to confront your limitations, rethink your workflow, improve your artistic skills, and understand why something didn’t work can be an incredibly valuable experience.

Of course, the opposite can be true as well. A tiny project can teach you something important that a larger one might never expose you to.

I just don’t understand why the internet sometimes treats making lots of tiny, quickly finished games as *the* correct way to learn game development, rather than one of several approaches.

Which brings me back to Unreal Engine.

Unreal is an incredibly powerful engine, but that’s also what makes it intimidating. There’s so much available that even the simplest ideas can start feeling like they deserve an entire production pipeline.

And because I’m studying game art, there’s also the visual side of things. I’m a pretty slow artist as is  so even making assets for something relatively simple can take a considerable amount of time. My coursework already demands a lot of that time and energy.

I’d like to make smaller, more experimental games in my free time, but I struggle with the idea of doing that in Unreal.

When you’re spending your education learning how to make polished, industry-standard work in an engine designed to support enormous productions, how do you switch off that mindset and just make something tiny?

How do you convince yourself that a game doesn’t need elaborate environments, carefully crafted assets, or a dozen interconnected systems to be worth making?

And perhaps more importantly, how do you avoid letting the sheer capabilities of the engine dictate the scope of your project?

I’m not against small games. Quite the opposite. I want to understand how to approach them in a way that actually complements what I’m already learning.

So I guess I have two questions:

1. Is Unreal Engine genuinely well suited to making tiny, experimental games? Or does its complexity make that process unnecessarily cumbersome compared to something like Godot or GameMaker?
2. How important is making lots of tiny games compared to making fewer, more polished and intricate ones? Especially when the latter is already part of a structured education?

I’m particularly interested in hearing from people who’ve worked on both quick prototypes and longer, more production-focused projects.

I don’t necessarily want to make *more* games just for the sake of finishing them. I want to become a better developer and artist, and I’m trying to figure out where small games fit into that.
```



document fetched 2026-10-22 00:27 · canonical https://reddit.com/r/gamedev/comments/1xbckp9/is_unreal_engine_bad_for_small_games
