Purging unused styles in Tailwind - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is purging unused styles in Tailwind CSS?

Purging unused styles means removing CSS classes that are not used in your project to make the final CSS file smaller and faster to load.

beginner

Why is purging unused styles important?

It reduces the size of CSS files, which improves website loading speed and performance, especially on mobile devices.

intermediate

How do you configure purging in Tailwind CSS?

You add the paths of your HTML, JavaScript, and template files in the content array inside tailwind.config.js. Tailwind scans these files to keep only used classes.

intermediate

What happens if you forget to include some files in the purge content paths?

Tailwind will remove classes used only in those files, causing missing styles and broken design in your website.

advanced

How can you safely use dynamic class names with Tailwind's purge?

You can use the safelist option in tailwind.config.js to list classes that should never be removed, even if not found in scanned files.

What is the main goal of purging unused styles in Tailwind CSS?

A Reduce CSS file size for better performance

B Add more CSS classes automatically

C Change colors of the website

D Create new animations

Purging removes unused CSS classes to reduce file size and improve loading speed.

Where do you specify which files Tailwind should scan for used classes?

A Inside CSS files

B In the HTML <head> section

C In the <code>content</code> array of <code>tailwind.config.js</code>

D In the JavaScript console

The content array tells Tailwind which files to scan for class names.

What can happen if you miss some files in the purge content paths?

A Classes used only in those files will be removed

B Tailwind will generate errors

C The website will load faster

D Unused classes will stay in the CSS

Tailwind removes classes not found in scanned files, causing missing styles if files are missed.

How do you keep dynamic class names from being purged?

A Write them only in HTML files

B Use the <code>safelist</code> option in <code>tailwind.config.js</code>

C Use inline styles instead

D Disable purging completely

The safelist option tells Tailwind to keep specified classes even if not found in scanned files.

When is purging unused styles usually done?

A During development

B When editing images

C When writing HTML

D Only in production builds

Purging is typically enabled in production to keep development fast and CSS files small for users.

Explain how purging unused styles works in Tailwind CSS and why it matters.

Think about how Tailwind scans your files to keep only what you use.

Describe how to handle dynamic class names so they are not removed during purging.

Consider classes generated by JavaScript or templates.

Practice

1. What is the main purpose of purging unused styles in Tailwind CSS?

easy

A. To remove unused CSS classes and make the site load faster

B. To add more CSS classes automatically

C. To change the colors of the website

D. To create new HTML elements

Solution

1. Step 1: Understand what purging means

   Purging means removing things that are not needed. In Tailwind CSS, it removes unused styles.

2. Step 2: Know why removing unused styles helps

   Removing unused styles makes the CSS file smaller, so the website loads faster.

3. Final Answer:

   To remove unused CSS classes and make the site load faster -> Option A

4. Quick Check:

   Purging = Remove unused styles = Faster site [OK]

Hint: Purging means removing unused CSS to speed up loading [OK]

Common Mistakes:

• Thinking purging adds styles instead of removing
• Confusing purging with changing colors or layout
• Believing purging creates new HTML elements

2. Which Tailwind config option tells Tailwind where to look for used CSS classes to purge?

easy

A. theme

B. content

C. plugins

D. variants

Solution

1. Step 1: Identify the config option for purging

   The content option lists files where Tailwind looks for class names to keep.

2. Step 2: Understand other options

   theme controls design tokens, plugins add features, variants control responsive states, so they don't control purging.

3. Final Answer:

   content -> Option B

4. Quick Check:

   content = files to scan for classes [OK]

Hint: Remember: content = where Tailwind looks for classes [OK]

Common Mistakes:

• Choosing theme instead of content
• Confusing plugins with purging config
• Using variants option wrongly

3. Given this Tailwind config snippet:

{
  content: ['./src/**/*.html'],
  theme: { extend: {} },
  plugins: []
}

Which files will Tailwind scan to keep CSS classes?

medium

A. All files in src folder and subfolders with .html extension

B. Only files named index.html in src folder

C. All JavaScript files in src folder

D. No files will be scanned

Solution

1. Step 1: Understand the glob pattern './src/**/*.html'

   This pattern means all .html files inside src and any subfolders.

2. Step 2: Match options with pattern meaning

   All files in src folder and subfolders with .html extension matches the pattern exactly. Options B and C are too narrow or wrong file types. No files will be scanned is incorrect.

3. Final Answer:

   All files in src folder and subfolders with .html extension -> Option A

4. Quick Check:

   ./src/**/*.html = all .html files in src and subfolders [OK]

Hint: ** means any folder depth, *.html means all HTML files [OK]

Common Mistakes:

• Thinking only top-level files are scanned
• Confusing file extensions scanned
• Assuming no files scanned without explicit mention

4. You set the content option incorrectly as ['./src/*.js'] but your classes are in HTML files inside subfolders. What problem will occur?

medium

A. Tailwind will include all styles correctly

B. Tailwind will generate duplicate CSS classes

C. Tailwind will throw a syntax error

D. Tailwind will purge needed styles causing missing styles on the site

Solution

1. Step 1: Analyze the content pattern './src/*.js'

   This pattern only scans JavaScript files directly inside src folder, not HTML or subfolders.

2. Step 2: Understand impact on purging

   Since HTML files with classes are not scanned, Tailwind thinks those classes are unused and removes them, causing missing styles.

3. Final Answer:

   Tailwind will purge needed styles causing missing styles on the site -> Option D

4. Quick Check:

   Wrong content path = missing styles after purge [OK]

Hint: Content must match all files with classes to avoid missing styles [OK]

Common Mistakes:

• Expecting Tailwind to scan files not listed
• Thinking wrong content causes errors instead of missing styles
• Assuming duplicate CSS classes will be generated

5. You want to purge unused styles but keep some dynamic classes added by JavaScript like bg-red-500 and text-xl. How can you ensure these classes are not removed?

hard

A. Write these classes directly in your HTML files only

B. Remove the content option entirely

C. Add these classes to the safelist option in Tailwind config

D. Use a plugin to disable purging

Solution

1. Step 1: Understand dynamic classes and purging

   Classes added by JavaScript are not in HTML files, so Tailwind may remove them during purge.

2. Step 2: Use safelist option to keep classes

   The safelist option lets you list classes to always keep, even if not found in scanned files.

3. Final Answer:

   Add these classes to the safelist option in Tailwind config -> Option C

4. Quick Check:

   Safelist = keep dynamic classes safe from purge [OK]

Hint: Use safelist to protect dynamic classes from purging [OK]

Common Mistakes:

• Removing content option disables purging but is not recommended
• Assuming writing classes in HTML fixes dynamic JS classes
• Thinking disabling purging plugin is best solution