To make a checkbox bigger in CSS, set the native input's width and height to the same pixel value, such as 32px. This enlarges the control while leaving the browser responsible for its checked state, form participation, and keyboard activation.
For a basic browser-styled checkbox, add this rule to your stylesheet:
input[type="checkbox"] { width: 32px; height: 32px; }
The declarations request a 32px square. Equal values keep the shape square, but native checkbox artwork can vary between browsers; use a complete custom appearance when the border, radius, colors, and check mark must be controlled.

Native sizing or a custom checkbox appearance?
Choose the styling level based on how much control you need. Changing the dimensions is the quickest solution, while a custom appearance gives you a predictable square, colors, and mark.
| Approach | What it changes | Good fit | Main caution |
|---|---|---|---|
| Width and height only | Enlarges the native input while the browser draws it | A quick change that keeps the default look | Exact native artwork varies by browser |
| Generated custom appearance | Controls the box, border, radius, three colors, check mark, and focus outline | A branded form with precise visual requirements | The real form states still need testing |
| Hand-written custom appearance | Uses custom selectors maintained by your development team | An established design system | More code and ongoing state maintenance |
The generated output includes box-sizing: border-box, so the selected size includes the visible border rather than adding space outside it.
The MDN appearance reference explains how the property affects native widget rendering, while the CSS Basic User Interface specification defines that behavior at the standards level. Setting appearance: none suppresses the browser's drawing without turning the native input into a generic element.
Make the checkbox bigger with generated CSS
-
Open the CSS Checkbox Generator and keep the control as input type="checkbox". Do not replace it with a generic div or image because that would remove native form behavior. Generation and copying happen entirely in the current browser tab, with no account, upload, or saved design state.
-
Set the square size to the value you want. The generator accepts whole pixels from 16px through 64px. This selection controls the visible custom checkbox box, including its border because the generated CSS uses border-box sizing.
-
Adjust the border and corner radius next. Border width accepts whole pixels from 1px through 6px, while radius ranges from 0% through 50%. These controls determine the outline shape independently of the selected box size.
-
Choose the accent, background, and checkmark colors. Every color must be a complete six-digit HEX value. Malformed colors, decimal entries where whole numbers are required, and out-of-range geometry are rejected instead of silently producing misleading code.
-
Exercise the live preview in its unchecked and checked states by clicking the box or its preview label. The preview applies the exact generated stylesheet through the scoped lizely-checkbox class, so it provides a useful check of the selected size, border, radius, and colors.
-
Copy the CSS and HTML separately. The two copy actions request clipboard permission independently. If permission is denied, both code blocks remain available for manual selection, and the page does not report a false success. The copied HTML contains no inline script.
-
Paste the CSS into a controlled stylesheet and the HTML into the real form. Rename the scoped class consistently in both blocks if needed, then replace the example label with wording that describes the actual choice. In a framework, translate class to className and connect checked or onChange behavior as required while retaining the native input and accessible label relationship.
-
Test the pasted result in the destination form. Use Tab to check focus order and Space to activate the control, then review contrast, 200% zoom, error handling, disabled behavior, and forced colors. The tool page contains several focusable controls, so its preview cannot substitute for testing the final form's order and instructions.
Treat the generated code as a clean baseline for the checkbox, not as a complete form-state system. It keeps the native element and supplies a focused appearance, but your surrounding application must still provide the required validation, help text, and contextual states.
Keep the larger checkbox labeled and keyboard-operable
The generated HTML places the checkbox input inside a label element with visible text. That label gives the control an accessible name, and clicking the text toggles the checkbox. Replace generic example wording with a meaningful description of the real choice before using the snippet in production.
Do not remove the generated :focus-visible outline. It appears with an offset and uses the selected accent color, giving keyboard users a visible indication of which control will respond to Space. The actual page background may require a different outline color or width; use the Color Contrast Checker to evaluate the final color pair against its real surroundings.
Keep the input native even when a framework offers a styled checkbox component. Framework code can manage the checked value and change event, but a custom div does not automatically provide the browser's checkbox semantics, Space activation, or form participation.
Check the result in the form where it will be used
The generator covers the basic unchecked, checked, and focus-visible appearances. It does not simulate every condition that a production form may require, so review the following coverage and add the missing behavior deliberately.
| State or condition | Generator coverage | Destination check |
|---|---|---|
| Unchecked | Included | Confirm the background and border at the final size |
| Checked | Included | Confirm the check mark, background, and border together |
| Focus-visible | Included | Reach it with Tab and inspect the outline and offset |
| Invalid or required | Not simulated | Add the relevant markup, error messaging, and validation behavior |
| Disabled | Not simulated | Add and test the disabled presentation and form behavior |
| Indeterminate | Not simulated | Implement and verify it if the product needs a mixed state |
| Forced colors | Not simulated | Test the colors applied by the operating system and browser |
Read-only, high-contrast, and other contextual conditions are also outside the preview. Check the accent, background, checkmark, border, focus indicator, surrounding page, hover state, error text, and disabled state in the final theme instead of assuming the preview represents all of them.
Operating systems and browsers may override custom colors in forced-colors mode. That change can be beneficial, so do not suppress useful accessibility overrides without a strong reason. At unusual zoom levels, device pixel ratios, or extreme border settings, antialiasing may also make one edge appear slightly heavier.
Fix the problems that appear after resizing
-
The box does not change. A later stylesheet rule may be overriding the width or height. Inspect the cascade and make sure the rule applies to the actual input rather than a wrapper.
-
The visible box is larger than the selected size. Confirm that the CSS includes box-sizing: border-box, or add it when adapting hand-written CSS.
-
The native artwork still looks inconsistent. Width and height alone do not create a fully controlled custom square. Use a complete custom appearance with checked and focus rules when exact geometry and colors matter.
-
Clicking the label does not toggle the control. Keep the input associated with the label through nesting or an equivalent explicit label relationship, and ensure there is only one control attached to that label.
-
The focus ring is missing. Avoid resetting the outline to none. Preserve or replace the generated focus-visible styling with an indicator that remains visible in the destination theme.
-
The mark or an edge looks uneven. The generated checkmark scales from the box size using deliberate local ratios, not a universal design standard. Review it at the actual zoom and rendering conditions before changing the generated geometry.
Choose the smallest change that solves the problem
When the default native checkbox is acceptable, equal width and height declarations are the smallest useful fix. They enlarge the input without removing its native checked state, keyboard activation, or form participation.
When you need an exact size, branded border and radius, coordinated colors, and synchronized CSS and HTML, the generator provides the relevant styling controls. In either approach, retain the native input, give it visible label text, preserve focus visibility, and test the completed form with real content.
Related reading: CSS Cubic Bezier Maker: Check Timing Before Copying.
Related reading: When to Generate a CSS Triangle Instead of Coding Manually.