Does MySQL int(1) Limit Your Integer Range? Understanding Display Width and ZEROFILL

When adding a user_id column, the author used int(1) and was told the size might be insufficient. This confusion is common because many developers mistakenly think the number in int(N) limits the stored value.

In MySQL an INT occupies 4 bytes; the unsigned maximum is 2^32‑1 = 4294967295. The display width (the number in parentheses) does not affect this range. A test table created with int(1) unsigned accepts the maximum value without error:

CREATE TABLE `user` (
  `id` int(1) unsigned NOT NULL AUTO_INCREMENT,
  PRIMARY KEY (`id`)
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4;

INSERT INTO `user` (`id`) VALUES (4294967295);
-- Query OK, 1 row affected

The insertion succeeds, proving that int(1), int(2), … int(10) all support the same numeric range.

The only time the number becomes meaningful is when the column is defined with ZEROFILL. In that case MySQL pads the displayed value with leading zeros to match the specified width.

CREATE TABLE `user` (
  `id` int(4) unsigned ZEROFILL NOT NULL AUTO_INCREMENT,
  PRIMARY KEY (`id`)
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4;

INSERT INTO `user` (`id`) VALUES (1),(10),(100),(1000);
SELECT * FROM `user`;
+------+
| id   |
+------+
| 0001 |
| 0010 |
| 0100 |
| 1000 |
+------+

The result shows that values are displayed with leading zeros, but the stored value remains the same (e.g., 1 is stored as 1, not 0001).

In summary, the numeric argument in INT(N) does not limit the column's capacity; it only influences display width when paired with ZEROFILL. Use ZEROFILL for fixed‑length numeric identifiers such as student numbers (001, 002, …) when you need zero‑padded output.