Skip to content

Guide · Open source

How to use magictools: find free game dev resources

Updated · written with AI from the project's own documentation and checked against our catalogue data

magictools is a curated Markdown list of game development resources, grouped into sections such as Graphics, Code, Audio, Board Games, and Learn. It is a link collection, not a program you install. This guide shows you how to read it, how to check each resource's license tag, and how to pick the right kind of item for your project.

magictoolsellisonleao/magictools · ★ 17.7k · MIT

Quick start

  1. 1Open the list. Go to the magictools README on GitHub and scroll to the table of contents.
  2. 2Pick a section. Choose the section that matches your need, such as Graphics for art or Learn for background reading.
  3. 3Read the license tag. Check the symbol at the start of the entry: free, open source, paid, or partially free.
  4. 4Read the description. Use the short description to confirm the file types, features, or purpose of the resource.
  5. 5Open the external site. Follow the link and read the license or terms on that site before you download or use anything.
  6. 6Record what you use. Note the source, license, and any attribution terms for each asset in your project.

What magictools is and is not

magictools is a list of links to external tools, asset sites, and learning resources for game development. The README describes it as a curated list to make magic happen in game development.

There is no software to download or run from this project. Each entry sends you to an outside site, where you use the tool or asset itself.

  • Works as a web page on GitHub: you read and click links.
  • Licensed under MIT, and the list itself is written in Markdown.
  • Each link points to a separate tool, asset site, or learning resource.

Find the section you need

The README has a table of contents that links to each section. Graphics is the largest, and it is split into subsections such as Assets/Placeholders, Spritesheet Tools, Bitmap Compression, Texture Tools, Character Generators, Tile/Level Editors, Animation, Modeling, Terrain Generators, and Voxel Editors.

Other top-level sections include Code (with Engines and Frameworks, and AI), Audio (with Collections and Music and Audio Editors), Board Games, Must see, Ads, and Learn.

  • Need sprites, icons, or textures? Start with Graphics, then Assets/Placeholders.
  • Packing sprite sheets? Look at Spritesheet Tools.
  • Want a starting point for theory? Look at Learn, which includes General Game Development and Computer Graphics.

Read the license tags before you use anything

Most entries begin with a symbol that describes the license status. The README defines four legends. Check the tag first, then open the link and read the actual license on the resource's own site, because the list does not replace that check.

Some categories, such as Blogs and Portals, Videos/Podcasts, Game Jams, and Communities, do not require a license tag under the submission rules.

  • :free: means Free.
  • :tada: means Open Source.
  • :moneybag: means Paid.
  • :money_with_wings: means Partially Free.
  • Partially Free items can include both free and paid parts, so read the terms before you rely on them.

Evaluate an entry before you commit to it

Each entry has a short description after the link. Some descriptions name the file formats or features, for example a layered psd file, PNG and ZMT files, or a PNG plus JSON export. Use these details to match an item to your engine and workflow.

The README says submissions must be explicitly about game development and must have at least 100 GitHub stars for repository links. It also says links are validated by a badge. It does not describe how each linked item is reviewed beyond that, so confirm the current terms yourself.

  • Confirm the file formats match your engine.
  • Open the license or terms page on the linked site.
  • Check whether the asset is for commercial use if your game will be sold.
  • Keep a record of the license for each asset you use.

What people use it for

  • An indie developer finds free 2D sprites or UI packs in Assets/Placeholders and checks each license before adding them to a game.
  • A hobbyist browses Spritesheet Tools to find a browser-based splitter or packer for their own sprite animations.
  • A student uses the Learn section as a map of general game development and computer graphics topics to study.
  • A developer scans Texture Tools for free or open source options before buying a paid texture generator.

Frequently asked questions

Is magictools free to use?

The list itself is MIT licensed, but the resources it links to vary. Each entry has a tag showing whether it is free, open source, paid, or partially free, so check the tag and the linked site's terms.

How do I install magictools?

You do not install it. magictools is a Markdown list of links with no software to run, so you read it on GitHub and open the resources you want.

What do the license symbols mean on magictools?

The README defines :free: as Free, :tada: as Open Source, :moneybag: as Paid, and :money_with_wings: as Partially Free. Some categories do not require a tag.

Are all resources on magictools free?

No. The list includes paid and partially free items, so you must check each tag before assuming a resource is free.

What are the alternatives to magictools?

The project names awesome-gamedev, awesome-game-dev, and free-for-dev as comparable lists. Like magictools, they are curated link collections.

Why might a link on magictools be outdated?

The README says links are checked with a validation badge, but it does not describe how each linked item is maintained. If a link fails or a site changes its terms, check the resource directly.

New agent skills, repos and AI tools — every week

The best new skills and open-source projects, the fastest-growing repos, and one free prompt. Five minutes to read. Unsubscribe anytime.

Our verdict

magictools suits indie developers, hobbyists, and students who want a organized map of game development resources and a quick license check. It is a poor choice if you want one installable tool or a verified review of every item. Read each license on the linked site before using an asset in a real project.

Install options & downloads