The fastest way to check for a Conan package

The simplest method is to run conan search from your command line. Type conan search package_name and Conan will tell you whether that package exists in your configured repositories, what versions are available, and where they live.

If the package exists, you'll see a list of versions with their remote locations. If it doesn't exist, Conan returns no results. This takes seconds and works offline if you've already downloaded package metadata.

For a quick check without leaving your terminal, this is the method most developers use. You don't need to edit any files or run a full build — just search and move on.

Key Takeaways

  • conan search package_name shows whether a package exists and lists all available versions in your configured repositories.
  • The Conan Center Index website lets you browse packages visually and see documentation, recipes, and version history without using the command line.
  • If a package doesn't exist in the default remote, you may need to add a custom repository or build the package yourself from a recipe.
  • Checking before you add a package to your conanfile.txt or conanfile.py saves time and prevents build failures later.

Using the Conan Center Index website

The Conan Center Index is the official repository where most public packages live. You can visit conan.io and search their package database directly in your browser. This shows you the same packages conan search finds, but with more detail: the recipe source code, what the package depends on, which platforms it supports, and release notes for each version.

This method is useful when you want to understand what a package does before you use it, or when you need to check whether it works on your operating system or architecture. The website also shows you the exact syntax to add the package to your conanfile.

If you're new to Conan or evaluating packages for a project, browsing the website first often saves time because you can read documentation and see examples before you commit to using something.

Checking what you already have installed locally

If you want to see packages you've already downloaded to your machine, use conan list instead of conan search. This shows only the packages in your local cache, not what's available remotely.

Run conan list "*" to see everything you have, or conan list package_name to check for a specific one. This is faster than searching remotes and useful when you're troubleshooting a build or checking whether you need to read something new.

What to do if the package doesn't exist

If conan search returns nothing, you have three options. First, check whether you spelled the name correctly — package names are case-sensitive and sometimes use underscores or hyphens in ways you might not expect. The Conan Center Index website is the best place to verify the exact name.

Second, the package might exist in a different remote repository that you haven't configured yet. Some organizations host private Conan repositories, and some packages live in community remotes. If you know the package should exist, ask your team or check the package's documentation for the correct remote URL.

Third, you can create your own Conan recipe and build the package yourself. This is more work but gives you full control. The Conan documentation includes templates for writing recipes, and many open-source projects already have community-maintained recipes you can adapt.

Adding a custom remote to search more repositories

By default, Conan searches the Conan Center Index. If you need packages from another source, add that remote with conan remote add remote_name remote_url. After that, conan search will include packages from both the default remote and your custom one.

You can list all your configured remotes with conan remote list and remove one with conan remote remove remote_name. The order matters — Conan searches remotes in the order you've added them, so if two remotes have the same package, the first one wins.

Checking package compatibility with your project

Finding a package is one thing; making sure it works with your setup is another. When you run conan search, you see version numbers, but not whether that version supports your operating system, compiler, or architecture. The Conan Center Index website shows this information under each package's details.

You can also add the package to your conanfile.txt or conanfile.py and run conan install with the --build=missing flag. Conan will tell you when ready if the package doesn't support your configuration, and you can try a different version or look for an alternative.

Using conanfile.py to check during development

If you're writing a conanfile.py, you can check for a package's existence as part of your build process. Add the package name to your requires list and run conan create or conan install. Conan will fail with a clear error if the package doesn't exist or isn't compatible, which tells you to search for an alternative before you invest more time.

This approach is slower than a quick conan search, but it's useful when you're evaluating multiple packages or when you want to test whether your entire dependency tree works together. You catch problems early instead of discovering them later in the build.

Frequently Asked Questions

Does conan search work if I'm offline?

It depends. If you've already downloaded package metadata from a remote, conan search can show you cached results. If you haven't, you need an internet connection. conan list always works offline because it only shows packages already on your machine.

What's the difference between conan search and conan list?

conan search looks in remote repositories (online) and shows what's available to read. conan list shows only packages already in your local cache. Use search to find new packages, and list to see what you already have.

Can I search for packages by what they do, not just by name?

The command line doesn't support keyword search — you need the exact package name. The Conan Center Index website has a search box where you can type partial names or descriptions, making it easier to find packages when you don't know the exact name.

What if a package exists but my version of Conan can't find it?

You may be using an older version of Conan that doesn't have access to newer packages. Update Conan with your package manager (pip, brew, or your distribution's package manager) and try again. You can also check whether the package requires a specific Conan version in its documentation.

How do I know if a package will work with my compiler and operating system?

The Conan Center Index website lists supported platforms for each package. You can also try adding it to your conanfile and running conan install — Conan will tell you when ready if there's a compatibility problem, and you can choose a different version or find an alternative package.