CC0 game assets, and what the license really lets you do
CC0 is the Creative Commons public domain dedication. A maker who applies it gives up their copyright in the work, as far as the law of their country allows, so anyone may copy it, change it and sell what they make with it, without asking and without a credit. For game assets, no license asks less of you.
Every item in the library, all released under CC0. 707 here.
Nature Kit
Dungeon Remastered
Tiny Dungeon
Character Pack: Adventurers
Pixel Platformer
Universal Animation Library 1 and 2
Medieval Hexagon Pack
Tower Defense Kit
Tiny Town
Character Pack: Skeletons
Isometric Miniature Dungeon
City Builder Bits
Prototype Bits
Halloween Bits
Restaurant Bits
Furniture Bits
Space Base Bits
Animal Pack Remastered (selection)
Scribble Platformer (selection)
Simple Space (selection)
Retro Game Music: Ending and Level 3
Animated Dragon
Animated Bull
Space Shooter Backgrounds
Tower Defense Kit, top down renders
Mini Dungeon, top down renders
Nature Kit, top down renders
Graveyard Kit, top down renders
Retro Coin and Pickup Sounds
Retro Damage and Defeat Sounds
Retro Door, Switch and Gadget Sounds
Retro Explosion and Hit Sounds
Retro Interface Sounds
Retro Jump and Movement Sounds
Retro Laser and Shot Sounds
Retro Power-up and Level-up Sounds
Healing and Magic Aura
Explosion with Debris and Shockwave
Campfire and Torch Fire
Impact Hits: Sparks, Magic and Slash
Swirling Magic Portal
Rain with Splashes
Screen Looks: Pixel, CRT and Outline
Gradient Sky with Clouds
Smoke Plume and Puffs
Falling Snow
Stylized Water
Weapon Trail
Everything in this library is CC0: 3D kits, sprites, animation clips, textures, skies, effects, sounds and music, made by Kenney, Kay Lousberg, Quaternius, Poly Haven, ambientCG, Juhani Junkala and Tyrbo. The legal text is short and worth a read at creativecommons.org.
What CC0 lets you do in a game
With a CC0 asset you may:
- Ship it in a game you sell on Steam, Google Play or the App Store, or in one you give away.
- Edit it as far as you like: recolor it, cut it apart, merge it with your own work.
- Show it in trailers, store screenshots, merchandise and printed art.
- Put the raw files in a public repository, an open source game or a template you share.
- Leave out the credit. A thank-you is welcome but never required.
The fourth point matters more than it looks. Many paid and free licenses forbid sharing the source files, which quietly rules out open source projects and moddable games. CC0 doesn't.
CC0 next to CC-BY and royalty free
- CC0: no conditions at all.
- CC-BY: free to use, commercial use included, but you must credit the author, link the license and say if you changed the work. Easy to honor for one file, easy to lose track of across a hundred.
- CC-BY-SA: as CC-BY, and anything you adapt from the asset must carry the same license. Fine for an open project, awkward for a closed one.
- CC-BY-NC: no commercial use, so not for a game you plan to sell.
- Royalty free: a promise about payment, not about freedom. You pay once or nothing and owe nothing per copy sold, but the license still sets its own rules on seats, credit or sharing.
When a store, a publisher or a lawyer asks what you used, CC0 is the shortest answer you can give.
What CC0 doesn't cover
CC0 waives copyright. Its text says outright that trademarks and patents are untouched, and no license can hand over rights the maker never held. In practice:
- Names and logos stay with their owners. Don't use a maker's name or logo in a way that suggests they made or endorse your game.
- Real brands inside an asset, a shop sign in a photo texture or a car modeled on a famous one, are still somebody's trademark. Swap them or blur them.
- People who appear in a photo or a scan may still have rights over their likeness.
- The uploader's honesty is the real guarantee. On a maker's own site, the maker says it. On an open archive, anyone can upload anything with a CC0 label on it.
Keep a record of where each asset came from
CC0 asks for no paperwork, so keep a little anyway. One spreadsheet or text file, with a row per pack:
- what it is, and where it sits in your project,
- who made it, and the page you downloaded it from,
- its license, and the day you got it.
It takes a minute a pack and pays off when a store reviewer asks, when a publisher checks your rights before signing, when a takedown notice lands on an asset that someone uploaded without the right to, or when you write your credits and want to thank the right people. Each item here already credits its maker and points to their own page, so the row is half written for you.
Questions people ask
Can I use CC0 assets in a commercial game?
Yes, with no conditions. Sell the game on any store, use the assets in its marketing, and owe nobody a share: CC0 has no royalty and no revenue limit.
Do I need to credit CC0 assets?
No, credit is optional. Many developers list the makers anyway, because a name in a released game is how small asset makers find new supporters.
If I change a CC0 asset, is my version mine?
What you add is your own work, but the original stays in the public domain. Anyone can take the same pack and make their own version, so CC0 gives you freedom, never exclusivity.
Is CC0 the same as public domain?
Nearly. Where a country's law lets a creator give up copyright, CC0 does exactly that. Where it doesn't, CC0 falls back to a license that grants the same freedoms, so the result for you is the same anywhere.
Why is everything in this library CC0?
So that nothing you download comes with a condition to track. One license on every shelf means you never have to check which file wants a credit before you ship.
Make a game with them
Make your gameSign in to get the plan and its concept art. Both are free.