> For the complete documentation index, see [llms.txt](https://docs.smartlauncher.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.smartlauncher.net/products/iconpackstudiofaq/icon-pack-studio-launcher-support/supported-launcher.md).

# Supported launchers

## Can I use Icon Pack Studio with my launcher?

Starting from September 2023, there are now two versions of Icon Pack Studio available:

1. **Play Store Version**\
   Restricted to only work with Smart Launcher
2. **Universal Version**\
   Supports all the launchers supported by the pre-2023 versions of IPS

For more information about the changes that led to this, please refer to this [**article**](/products/iconpackstudiofaq/icon-pack-studio-launcher-support.md).

## Will Icon Pack Studio Universal Work With My Launcher?

Icon Pack Studio Universal has been designed to work with any launcher. However, in order to use your icon packs with your launcher, your launcher needs to support the Icon Pack Studio format, which is one of the most common icon pack formats in the Android market.

If your launcher is listed as not compatible, we apologize but we cannot fix the problem. Only your launcher developer can solve it.

If your launcher is not in the list, it means it has not been tested with Icon Pack Studio. It may work, but we cannot guarantee it.<br>

**Compatible launchers**

* Smart Launcher (of course) (ginlemon.flowerfree)
* Nova Launcher (com.teslacoilsw\.launcher)
* Niagara Launcher (bitpit.launcher)
* Action Launcher (com.actionlauncher.playstore)
* Lawnchair Launcher (ch.deletescape.lawnchair.plah)
* Hyperion Launcher (projekt.launcher)
* Poco Launcher (com.mi.android.globallauncher)
* Miui Launcher (com.miui.home)
* ADW Launcher (org.adwfreak.launcher)
* ADW Launcher 2 (org.adw\.launcher)
* Microsoft Launcher (com.microsoft.launcher)
* Evie Launcher (is.shortcut)
* Total Launcher (com.ss.launcher2)
* Niagara Launcher (bitpit.launcher)
* Square Home Launcher (com.ss.squarehome2)
* Apex Launcher (com.anddoes.launcher)
* Apex Launcher Classic (com.anddoes.gingerapex)

**Not compatible launchers**

* Pixel Launcher (com.google.android.apps.nexuslauncher)
* AOSP Launcher (com.android.launcher3)
* Huawei Launcher (com.huawei.android.launcher)
* Sony Launcher (com.sonymobile.home)
* Yahoo Japan Launcher (com.buzzpia.aqua.launcher.buzzhome)
* +Home Launcher (jp.co.a\_tm.android.launcher)
* Samsung One UI Home (com.sec.android.app.launcher)
* LINE/dodol Launcher - (com.campmobile.launcher)
* Yandex Launcher -(com.yandex.launcher)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.smartlauncher.net/products/iconpackstudiofaq/icon-pack-studio-launcher-support/supported-launcher.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.