> For the complete documentation index, see [llms.txt](https://elixir.petrolidas.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://elixir.petrolidas.com/bits-and-pieces/how-to-remove-tailwind-from-a-phoenix-project.md).

# How to remove Tailwind from a Phoenix project

There's a chance you have an existing Phoenix project that has been created with the default option of having TailwindCSS integrated, but you would like to go vanilla CSS.

## Steps

1. Remove `:tailwind` from `mix.exs`
2. Remove related commands from `aliases` in  `mix.exs` (make sure to preserve any `esbuild` builds if you are using that).
3. Remove `@import "tailwindcss/...` from `app.css`
4. Open `js/app.js` and add `import "../css/app.css"` to it.
5. Delete file `/assets/tailwind.config.js`
6. Remove block starting with   `config :tailwind` from `config.exs`
7. Remove `tailwind: {Tailwind, :install_and_run, [:default, ~w(--watch)]}` from `watchers` inside `dev.exs`
8. Run `mix deps.clean --unlock --unused`

{% hint style="info" %}
You may have to fix layout related issues, how you render flash messages, and adjust `core_components.exs.`

`Original solution found in` [`Elixir Forums`](https://elixirforum.com/t/how-to-remove-tailwind-from-phoenix-completely-i-only-want-vanilla-css/54551)`.`
{% endhint %}


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://elixir.petrolidas.com/bits-and-pieces/how-to-remove-tailwind-from-a-phoenix-project.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.