Custom spacing scale in Tailwind

Introduction

Custom spacing scale lets you create your own sizes for margins, padding, and gaps. This helps keep your design consistent and unique.

You want your website spacing to match your brand style exactly.

You need spacing sizes that Tailwind doesn't have by default.

You want to keep spacing consistent across different parts of your site.

You want to make your code easier to read by using meaningful spacing names.

You want to avoid repeating the same custom values everywhere.

Syntax

Tailwind

module.exports = {
  theme: {
    extend: {
      spacing: {
        '72': '18rem',
        '84': '21rem',
        '96': '24rem',
        '128': '32rem'
      }
    }
  }
}

Put your custom spacing inside the extend.spacing section to add to the default scale.

Use keys as strings for spacing names and values as CSS size units like rem, px, or %.

Examples

Adds a new spacing size named 72 equal to 18rem.

Tailwind

module.exports = {
  theme: {
    extend: {
      spacing: {
        '72': '18rem'
      }
    }
  }
}

Creates custom spacing names sm, md, and lg with pixel values.

Tailwind

module.exports = {
  theme: {
    extend: {
      spacing: {
        'sm': '8px',
        'md': '16px',
        'lg': '24px'
      }
    }
  }
}

Defines a spacing size called half that equals 50% of the parent size.

Tailwind

module.exports = {
  theme: {
    extend: {
      spacing: {
        'half': '50%'
      }
    }
  }
}

Sample Program

This example shows two boxes with very large padding using custom spacing sizes 72 and 84. The spacing is added to Tailwind's default scale using extend.spacing.

Tailwind

<!DOCTYPE html>
<html lang="en">
<head>
  <meta charset="UTF-8" />
  <meta name="viewport" content="width=device-width, initial-scale=1" />
  <title>Custom Spacing Scale Example</title>
  <script src="https://cdn.tailwindcss.com"></script>
  <script>
    tailwind.config = {
      theme: {
        extend: {
          spacing: {
            '72': '18rem',
            '84': '21rem'
          }
        }
      }
    }
  </script>
</head>
<body class="p-8">
  <div class="bg-blue-200 p-72 text-center">
    This box has padding of 18rem (custom spacing 72).
  </div>
  <div class="bg-green-200 mt-8 p-84 text-center">
    This box has padding of 21rem (custom spacing 84).
  </div>
</body>
</html>

Important Notes

Always use extend to add spacing so you don't remove Tailwind's default sizes.

You can use any CSS unit like rem, px, %, or em for spacing values.

Use meaningful names for spacing to make your code easier to understand.

Summary

Custom spacing scale lets you add your own spacing sizes to Tailwind.

Put your sizes inside extend.spacing in the Tailwind config.

Use your custom spacing classes like p-72 or m-84 in your HTML.

Practice

1. What is the main purpose of adding a custom spacing scale in Tailwind CSS?

easy

A. To create new spacing sizes beyond the default ones

B. To change the color palette of the project

C. To add new font families

D. To enable JavaScript animations

Solution

1. Step 1: Understand Tailwind spacing scale

   Tailwind provides default spacing sizes, but sometimes you need sizes not included by default.

2. Step 2: Purpose of custom spacing scale

   Adding a custom spacing scale lets you define new spacing values to use in classes like padding or margin.

3. Final Answer:

   To create new spacing sizes beyond the default ones -> Option A

4. Quick Check:

   Custom spacing scale = new spacing sizes [OK]

Hint: Custom spacing adds new size options beyond defaults [OK]

Common Mistakes:

• Confusing spacing scale with colors or fonts
• Thinking it enables animations
• Assuming it changes existing default sizes

2. Which of the following is the correct way to add a custom spacing value of 72 (18rem) in Tailwind config?

easy

A. "extend: { colors: { 72: '18rem' } }" inside tailwind.config.js

B. "spacing: { 72: '18rem' }" at the root of tailwind.config.js

C. "extend: { spacing: { 72: '18rem' } }" inside tailwind.config.js

D. "extend: { fontSize: { 72: '18rem' } }" inside tailwind.config.js

Solution

1. Step 1: Locate correct config property for spacing

   Custom spacing values go inside the extend.spacing object in tailwind.config.js.

2. Step 2: Check syntax correctness

   "extend: { spacing: { 72: '18rem' } }" inside tailwind.config.js correctly places 72: '18rem' inside extend.spacing. Other options put spacing at root or wrong keys like colors or fontSize.

3. Final Answer:

   "extend: { spacing: { 72: '18rem' } }" inside tailwind.config.js -> Option C

4. Quick Check:

   Custom spacing inside extend.spacing [OK]

Hint: Custom spacing must be inside extend.spacing [OK]

Common Mistakes:

• Placing spacing directly at root instead of extend
• Adding spacing under colors or fontSize
• Using incorrect syntax or missing quotes

3. Given this Tailwind config snippet:

{
  extend: {
    spacing: {
      84: '21rem'
    }
  }
}

What will be the padding size applied by the class p-84 in HTML?

medium

A. 8.4rem padding on all sides

B. No padding applied, class invalid

C. 2.1rem padding on all sides

D. 21rem padding on all sides

Solution

1. Step 1: Understand custom spacing value

   The config defines spacing 84 as '21rem', so class p-84 means padding: 21rem.

2. Step 2: Interpret class effect

   Class p-84 applies padding of 21rem on all sides of the element.

3. Final Answer:

   21rem padding on all sides -> Option D

4. Quick Check:

   p-84 = padding 21rem [OK]

Hint: Class p-84 uses spacing 84 value exactly [OK]

Common Mistakes:

• Confusing 84 with 8.4 or 2.1 rem
• Thinking class is invalid without default spacing
• Assuming padding applies only to one side

4. You added this to your tailwind.config.js:

extend: {
  spacing: {
    100: '25rem'
  }
}

But using m-100 in HTML does not apply margin. What is the likely problem?

medium

A. The spacing value '25rem' is invalid

B. You forgot to restart the build process after config change

C. Class name should be m-10 instead of m-100

D. Tailwind does not support custom spacing values

Solution

1. Step 1: Check if config syntax is correct

   The config syntax is correct; 100: '25rem' inside extend.spacing is valid.

2. Step 2: Understand Tailwind build process

   After changing tailwind.config.js, you must restart the build or dev server to apply changes.

3. Final Answer:

   You forgot to restart the build process after config change -> Option B

4. Quick Check:

   Restart build after config update [OK]

Hint: Restart build after config edits to apply changes [OK]

Common Mistakes:

• Assuming spacing value format is wrong
• Using wrong class name syntax
• Thinking Tailwind disallows custom spacing

5. You want to add two custom spacing sizes: 72 (18rem) and 84 (21rem). How should you write the extend.spacing part in tailwind.config.js to use both sizes correctly?

hard

A. { extend: { spacing: { 72: '18rem', 84: '21rem' } } }

B. { extend: { spacing: { '72': 18, '84': 21 } } }

C. { spacing: { 72: '18rem', 84: '21rem' } }

D. { extend: { spacing: [72, 84] } }

Solution

1. Step 1: Correct syntax for multiple custom spacings

   Custom spacing values go inside extend.spacing as key-value pairs with keys as numbers and values as strings with units.

2. Step 2: Analyze incorrect options

   Placing spacing at the root overrides defaults. Using string keys or numeric values without units is invalid. Arrays are not supported for spacing definitions.

3. Final Answer:

   { extend: { spacing: { 72: '18rem', 84: '21rem' } } } -> Option A

4. Quick Check:

   Multiple spacings as key-value pairs in extend.spacing [OK]

Hint: Use object with keys and rem strings inside extend.spacing [OK]

Common Mistakes:

• Using numbers without units for spacing values
• Placing spacing outside extend
• Using arrays instead of objects for spacing