Introduction

Extra spacing between UITableView sections is a common layout issue in settings screens and form-heavy interfaces. The exact gap depends on table style, iOS version, and estimated height behavior, so one tweak is often not enough. A stable solution combines style choice, delegate height methods, and iOS-specific padding controls.

Core Sections

Start with table style and design intent

Section spacing behavior differs between .plain and .grouped styles. If design allows dense layout, .plain is easier to keep compact. If grouped visual blocks are required, spacing can still be reduced with explicit header and footer configuration.

1import UIKit
2
3let tableView = UITableView(frame: .zero, style: .plain)
4tableView.separatorStyle = .singleLine

Choosing style first prevents unnecessary override complexity later.

Collapse section headers and footers deliberately

Use delegate methods to return very small heights and provide empty views. Returning exact zero can trigger fallback defaults in some configurations.

1final class CompactTableVC: UITableViewController {
2    override func tableView(_ tableView: UITableView, heightForHeaderInSection section: Int) -> CGFloat {
3        .leastNormalMagnitude
4    }
5
6    override func tableView(_ tableView: UITableView, heightForFooterInSection section: Int) -> CGFloat {
7        .leastNormalMagnitude
8    }
9
10    override func tableView(_ tableView: UITableView, viewForHeaderInSection section: Int) -> UIView? {
11        UIView(frame: .zero)
12    }
13
14    override func tableView(_ tableView: UITableView, viewForFooterInSection section: Int) -> UIView? {
15        UIView(frame: .zero)
16    }
17}

This is the most reliable baseline for minimizing section gaps.

Handle iOS 15 section header top padding

On iOS 15 and newer, plain tables add default sectionHeaderTopPadding. Set it explicitly when compact spacing is required.

1override func viewDidLoad() {
2    super.viewDidLoad()
3
4    if #available(iOS 15.0, *) {
5        tableView.sectionHeaderTopPadding = 0
6    }
7}

Without this, you may still see a top gap even with custom header heights.

Control estimated heights to avoid layout jumps

Estimated section heights can create temporary spacing jumps during reload and scrolling. Disable or minimize estimates if visual stability is critical.

tableView.estimatedSectionHeaderHeight = 0
tableView.estimatedSectionFooterHeight = 0
tableView.estimatedRowHeight = 44

Use fixed row heights only when content is predictable. For dynamic text, keep row estimation but lock section estimates.

Check inset and safe-area side effects

Sometimes the perceived section gap is actually content inset from container controllers. Inspect contentInset, adjustedContentInset, and navigation container behavior.

tableView.contentInset = .zero
tableView.scrollIndicatorInsets = .zero

In complex layouts, verify spacing in both portrait and landscape because safe-area behavior changes.

Package layout settings into reusable configuration

If multiple view controllers need dense tables, create a shared setup function or subclass. This avoids inconsistent spacing behavior across screens.

A compact table configuration utility should include style defaults, padding rules, estimated height settings, and iOS 15 adjustments.

Test with realistic data volume

Spacing can look correct with one section and drift with many sections or dynamic updates. Test with multiple section counts, long text rows, and live reload scenarios.

Snapshot tests can help lock visual spacing behavior after refactors.

Distinguish visual spacing from separator rendering

Design reviews sometimes report extra spacing when the actual issue is separator inset or background contrast. Validate row separator style, section background color, and grouped container margins before changing section height logic again.

By separating these concerns, you avoid over-tuning layout code to fix what is actually a visual styling mismatch.

Common Pitfalls

• Returning zero header heights and expecting uniform behavior across styles.
• Forgetting iOS 15 sectionHeaderTopPadding when using plain tables.
• Confusing content inset spacing with section header spacing.
• Leaving estimated section heights enabled in dynamic update-heavy screens.
• Repeating one-off spacing tweaks instead of reusing a consistent setup.

Summary

• Start with the correct table style for your intended visual density.
• Reduce section spacing using explicit header and footer heights plus empty views.
• Set iOS 15 top padding to zero for compact plain table layouts.
• Tune estimated heights and insets to avoid visual jumps.
• Reuse one compact configuration pattern across screens for consistency.