Introduction

UITableView separators are inset by default to align with text content. If your design needs edge-to-edge lines, you must configure both table-level and cell-level margins because either layer can reintroduce padding. A reliable setup also accounts for iOS version differences, grouped styles, and custom cells.

Why Separators Stay Inset

Many developers set one property and expect all separators to become full width, but UITableView rendering depends on multiple values:

• 'separatorInset on the table.'
• 'layoutMargins on the table.'
• 'layoutMargins and separatorInset on each cell.'
• Table style and iOS behavior around edge references.

If any of these keep non-zero margins, separators may still appear short.

Baseline Table Configuration

Start with table-level zero insets in viewDidLoad.

1import UIKit
2
3final class SettingsViewController: UITableViewController {
4    override func viewDidLoad() {
5        super.viewDidLoad()
6
7        tableView.separatorInset = .zero
8        tableView.layoutMargins = .zero
9        tableView.preservesSuperviewLayoutMargins = false
10
11        if #available(iOS 15.0, *) {
12            tableView.separatorInsetReference = .fromCellEdges
13        }
14    }
15}

This handles many simple list screens and sets a stable baseline.

Enforce Cell-Level Margins in willDisplay

Custom cells or reused cells can carry old margin values. Reset margins in willDisplay to keep behavior consistent.

1override func tableView(_ tableView: UITableView,
2                        willDisplay cell: UITableViewCell,
3                        forRowAt indexPath: IndexPath) {
4    cell.separatorInset = .zero
5    cell.layoutMargins = .zero
6    cell.preservesSuperviewLayoutMargins = false
7
8    cell.contentView.layoutMargins = .zero
9    cell.contentView.preservesSuperviewLayoutMargins = false
10}

Doing this at display time is a practical guard for mixed cell types.

Custom Separator View for Precise Control

When you need exact thickness, color, or leading behavior, disable system separators and draw your own line inside the cell.

1import UIKit
2
3final class FullWidthCell: UITableViewCell {
4    private let separator = UIView()
5
6    override init(style: UITableViewCell.CellStyle, reuseIdentifier: String?) {
7        super.init(style: style, reuseIdentifier: reuseIdentifier)
8
9        separator.backgroundColor = UIColor.separator
10        separator.translatesAutoresizingMaskIntoConstraints = false
11        contentView.addSubview(separator)
12
13        NSLayoutConstraint.activate([
14            separator.leadingAnchor.constraint(equalTo: contentView.leadingAnchor),
15            separator.trailingAnchor.constraint(equalTo: contentView.trailingAnchor),
16            separator.bottomAnchor.constraint(equalTo: contentView.bottomAnchor),
17            separator.heightAnchor.constraint(equalToConstant: 0.5)
18        ])
19    }
20
21    required init?(coder: NSCoder) {
22        fatalError("init(coder:) has not been implemented")
23    }
24
25    func setSeparatorHidden(_ hidden: Bool) {
26        separator.isHidden = hidden
27    }
28}

If you hide the last row separator for visual polish, add a simple setSeparatorHidden call in cellForRowAt.

Grouped Styles and Safe Area Effects

insetGrouped style can add visual spacing that makes separator behavior feel inconsistent. If your screen requires strict full-width lines, test each style explicitly:

• '.plain usually matches full-width expectations fastest.'
• '.grouped and .insetGrouped may require custom separators for exact output.'

Also verify on devices with different safe-area sizes. Separator width can look correct on one simulator but visually clipped on another when constraints are tied to the wrong view.

Debugging Misalignment Quickly

For layout debugging, add temporary borders:

cell.contentView.layer.borderColor = UIColor.systemRed.cgColor
cell.contentView.layer.borderWidth = 0.5

If the border reaches full width but separator does not, separator constraints or inset values are wrong. If both are inset, margins are still active at table or cell level.

Remove debug borders after verification.

Accessibility and Dynamic Type Checks

Full-width separators should remain correct when text size increases, rows become taller, or layout direction switches right-to-left. Always verify with:

• Dynamic type large text settings.
• Light and dark mode separator contrast.
• Right-to-left locale.

Visual separators are part of readability, so this is not only cosmetic.

Common Pitfalls

• Setting table separator inset once and forgetting cell-level margin overrides.
• Assuming grouped styles will match plain table separator behavior.
• Mixing system separators and custom lines in the same screen.
• Not testing on iOS versions with different separator reference behavior.
• Debugging by guesswork instead of inspecting layout margins and constraints.

Summary

• Full-width separators require both table and cell margin alignment.
• Reset separator and layout margins consistently in viewDidLoad and willDisplay.
• Use custom separator views when design requires exact control.
• Validate grouped styles, safe-area behavior, and accessibility scenarios.
• Add temporary visual debugging aids to isolate alignment issues quickly.