How many spaces is a tab? Usually, a tab appears as 2, 4, or 8 columns, depending on the editor or viewer. Technically, however, a tab is one character—not a fixed number of space characters.

The displayed width and the stored character are separate. A tab setting controls where the next tab stop appears, while inserting spaces places individual space characters in the file.

How many spaces is a tab?

A tab character is commonly represented as U+0009. In UTF-8, it occupies one byte, 0x09. That character does not contain instructions such as “insert four spaces.” The program displaying it decides how far to move the text.

If the tab width is set to four columns, tab stops occur every four columns. A tab at the beginning of a line may therefore appear four columns wide. A tab typed after text that already occupies two columns may appear only two columns wide, because it moves the cursor to the next tab stop.

Spaces behave differently. Each ordinary space is a separate character, usually U+0020, and occupies one column in a monospace font. Four inserted spaces remain four characters regardless of the viewer’s tab setting.

In a monospace comparison, visible markers make the difference clear: one tab [⇥]X versus four literal spaces [␠␠␠␠]X. The ⇥ marker represents one tab character, while each ␠ marker represents one space. They may create the same indentation at a four-column setting, but the file contains different characters.

How many spaces are in a tab at 2, 4, or 8 columns?

There are no spaces “inside” a tab. The numbers 2, 4, and 8 describe common display settings:

• 2 columns: Often used when compact indentation is important, such as in many web and configuration files.
• 4 columns: A common general-purpose choice that provides clearer nesting without excessive horizontal movement.
• 8 columns: A traditional default in many terminals and tools, making tabs highly visible but potentially creating wide indentation.

A setting of four does not guarantee that every tab occupies four visible columns. It means the display uses tab stops four columns apart. The tab’s apparent width depends on its position on the line and the current display settings.

How does tab width in spaces affect source files?

Source files normally store the tab character itself, not its rendered width. The file may contain a sequence such as one tab, two tabs, or a mixture of tabs and spaces. An editor then renders those characters using its configured tab size.

As a result, the same file can look different in two editors. A line indented with one tab may align at column 4 in one editor and column 8 in another. Code that relies on visual alignment, including comments or continued expressions, can become misleading when the tab setting changes.

Project formatters and editor settings can also rewrite indentation. A formatter may convert tabs to spaces, convert leading spaces to tabs, or enforce a selected indentation size. These rules affect the characters saved to the file, not just their appearance. A file’s visual layout is therefore controlled by both its contents and the tools that interpret or format it.

How do you keep indentation consistent across editors?

Choose one project-wide indentation convention and configure every relevant tool to follow it. The important settings are usually named tab size, indent size, and insert spaces or insert tabs.

• Decide whether indentation should use tabs, spaces, or a defined combination.
• Set the editor’s tab display width to the project’s documented value, such as 2 or 4 columns.
• Set automatic indentation to insert the chosen character type rather than relying on each editor’s default.
• Configure the project formatter to preserve or normalize that convention when files are saved.
• Check existing files for mixed leading tabs and spaces before applying broad conversion.

For a spaces-only convention, a four-level indent means four literal spaces per level. For a tabs-only convention, one tab may represent one indentation level while its visual width remains configurable. Keeping those choices explicit prevents indentation from changing when the file moves between editors, terminals, and code-review tools.