Swift Struct Memberwise Initializers Explained with Examples

By Murat Bo · Updated Oct 17, 2026 · Copy for AI · Markdown

Swift structs often get a useful initializer automatically: a memberwise initializer that accepts values for the struct's stored properties. This feature makes custom types easier to create, reduces boilerplate, and helps you build clear, predictable data models. In this article, you will learn when Swift generates a memberwise initializer, how to use it, what changes when you add your own init, and the mistakes that commonly confuse beginners.

Quick answer: A Swift struct memberwise initializer is an automatically generated initializer that takes one parameter for each stored property. Swift creates it for structs by default, but its exact behavior depends on property defaults, access control, and whether you define custom initializers in the struct itself.

1. What Is a Swift Struct Memberwise Initializer?

A memberwise initializer is a synthesized initializer that Swift creates for a struct when it can determine how to initialize all of the struct's stored properties. Instead of writing a full custom initializer by hand, you can often create instances by passing values directly for each property.

• It is automatically created for many structs.
• It uses the struct's stored properties as initializer parameters.
• It helps you create instances without writing repetitive setup code.
• It is different from the default no-argument initializer, which only exists in certain cases.
• It applies to structs, not classes in the same automatic way.

For example, if a struct has name and age properties, Swift can often synthesize an initializer that looks like init(name:age:).

struct User {
    let name: String
    let age: Int
}

let user = User(name: "Maya", age: 30)

Even though no initializer is written in the struct, Swift can still create one for you here.

A common beginner confusion is the difference between a memberwise initializer and a default initializer. A memberwise initializer accepts property values as arguments. A default initializer is a no-argument initializer, and Swift only synthesizes that when every stored property already has a default value.

2. Why Memberwise Initializers Matter

Memberwise initializers matter because they make structs convenient and expressive. In Swift, structs are commonly used for data models such as users, products, coordinates, settings, and configuration values. When Swift generates the initializer automatically, you can focus on the data itself instead of writing repetitive setup code.

They are especially useful when:

• You have plain data types with a few stored properties.
• You want clear instance creation at the call site.
• You want to reduce boilerplate in small and medium-sized models.
• You want the compiler to keep the initializer in sync with the stored properties.

They are less ideal when:

• You need validation before assignment.
• You want a different public API than the stored property list.
• You need to hide some implementation details from callers.

In those cases, you may prefer a custom initializer.

3. Basic Syntax

The core idea is simple: define a struct with stored properties, and Swift may synthesize an initializer whose parameters match those properties.

A minimal example

This struct has two stored properties and no custom initializer. Swift generates the memberwise initializer automatically.

struct Point {
    var x: Int
    var y: Int
}

let originOffset = Point(x: 10, y: 20)

The call uses argument labels that match the property names. That is what makes the initializer “memberwise”: each member, or stored property, becomes part of the initializer signature.

Properties with default values

If some stored properties have default values, the synthesized memberwise initializer can often let you omit those arguments.

struct Size {
    var width: Int = 100
    var height: Int = 100
}

let defaultSize = Size()
let customWidth = Size(width: 200)
let fullCustom = Size(width: 200, height: 300)

Because both properties already have default values, this struct can also use a no-argument default initializer.

Memberwise initializer vs custom initializer

When you write your own initializer inside the struct declaration, the automatically synthesized memberwise initializer is no longer available in that same declaration.

struct Product {
    let name: String
    let price: Double

    init() {
        name = "Unknown"
        price = 0.0
    }
}

After adding this custom initializer, Product(name:price:) is not automatically available from that struct declaration.

4. Step-by-Step Examples

Example 1: A simple data model

This first example shows the most basic and most common use. The struct stores data, and Swift synthesizes the initializer.

struct Book {
    let title: String
    let author: String
    let pages: Int
}

let book = Book(title: "Swift Basics", author: "Alex Kim", pages: 240)
print(book.title)

Swift Basics

This is ideal for plain data types because the initializer matches the properties exactly and stays easy to read.

Example 2: Using default property values

Here, some properties have defaults. That makes the memberwise initializer more flexible.

struct Account {
    var username: String
    var isPremium: Bool = false
    var loginCount: Int = 0
}

let newUser = Account(username: "sam")
let premiumUser = Account(username: "jordan", isPremium: true, loginCount: 12)

The first instance uses only the required property. The second overrides the defaults by supplying all values.

Example 3: Restoring the memberwise initializer with an extension

A subtle but important rule in Swift is that if you put custom initializers in an extension instead of in the original struct body, the synthesized memberwise initializer can still remain available.

struct Rectangle {
    var width: Double
    var height: Double
}

extension Rectangle {
    init(square: Double) {
        self.width = square
        self.height = square
    }
}

let box = Rectangle(width: 10.0, height: 20.0)
let square = Rectangle(square: 15.0)

This gives you both the memberwise initializer and the custom convenience initializer.

Example 4: Private property changes what callers can do

Access control affects the synthesized initializer. A property with a more restrictive access level can make the memberwise initializer less accessible than you expect.

struct Profile {
    let username: String
    private let internalID: Int
}

// error: 'Profile' initializer is inaccessible due to 'private' protection level
let profile = Profile(username: "lee", internalID: 42)

This call does not compile. Because internalID is private, the synthesized memberwise initializer is private too, so only code inside Profile itself (including its extensions in the same file) can call it. In practice, if you need a stable public initializer, write one explicitly.

5. Practical Use Cases

• Modeling API response data with structs such as User, Post, or Comment.
• Creating geometry or layout values such as points, sizes, or ranges.
• Storing app configuration values with a few optional defaults.
• Representing form input before validation or submission.
• Building lightweight domain models such as products, invoices, addresses, and settings.

These cases work well because the property list already describes how an instance should be constructed.

6. Common Mistakes

Mistake 1: Assuming the memberwise initializer always exists after adding a custom init

Many beginners add a custom initializer inside the struct and then expect the synthesized memberwise initializer to still be available.

Problem: Once you define an initializer in the main struct declaration, Swift does not keep the automatically synthesized memberwise initializer there. Calls such as TypeName(property:) can then fail with errors like “extra arguments in call” or “missing argument for parameter”.

struct Employee {
    let name: String
    let id: Int

    init() {
        name = "Unknown"
        id = 0
    }
}

let worker = Employee(name: "Ava", id: 1001)

error: argument passed to call that takes no arguments

Fix: Either write the memberwise-style initializer yourself or move the extra initializer into an extension so Swift can keep the synthesized one.

struct Employee {
    let name: String
    let id: Int
}

extension Employee {
    init() {
        self.name = "Unknown"
        self.id = 0
    }
}

let worker = Employee(name: "Ava", id: 1001)

The corrected version works because the custom initializer lives in an extension, so the synthesized memberwise initializer remains available.

Mistake 2: Confusing the memberwise initializer with a no-argument default initializer

Developers often expect every struct to support TypeName(), even when not all properties have default values.

Problem: A struct only gets a no-argument default initializer if every stored property has a default value. Without that, calling TypeName() causes a compile-time error because Swift still needs values for required properties.

struct Article {
    let title: String
    let wordCount: Int
}

let draft = Article()

error: missing arguments for parameters 'title', 'wordCount' in call

Fix: Supply values through the memberwise initializer, or provide defaults for every stored property if a no-argument initializer is what you want.

struct Article {
    let title: String
    let wordCount: Int
}

let draft = Article(title: "Getting Started", wordCount: 1200)

The corrected version works because all required stored properties receive values during initialization.

Mistake 3: Expecting the synthesized initializer to be public automatically

When building reusable modules, developers often assume that a public struct also gets a public memberwise initializer.

Problem: The synthesized memberwise initializer for a struct is not automatically exposed as a public API in the way many beginners expect. This can lead to access control errors when trying to create the struct from another module.

public struct Config {
    public let host: String
    public let port: Int
}

Fix: If the struct is part of a public API, write an explicit public init yourself.

public struct Config {
    public let host: String
    public let port: Int

    public init(host: String, port: Int) {
        self.host = host
        self.port = port
    }
}

The corrected version works because the initializer is now explicitly part of the public API.

7. Best Practices

Use memberwise initializers for simple data structs

If your struct mostly stores values and does not need validation or special construction logic, let Swift synthesize the initializer instead of writing boilerplate.

struct Address {
    let street: String
    let city: String
    let zipCode: String
}

This keeps the code short and makes the construction API match the stored data exactly.

Use default values to reduce repetitive arguments

When a property usually has the same value, give it a default so callers only provide the values that really vary.

struct Theme {
    var fontSize: Int = 16
    var isDarkMode: Bool = false
}

let standardTheme = Theme()
let darkTheme = Theme(isDarkMode: true)

This improves readability because callers do not need to repeat obvious defaults.

Write explicit initializers for public or validated APIs

If your struct is part of a library or needs business rules, write the initializer yourself so the API stays stable and intentional.

struct Temperature {
    let celsius: Double

    init(celsius: Double) {
        self.celsius = celsius
    }
}

This makes the construction rules explicit rather than relying on synthesis that may change when properties change.

8. Limitations and Edge Cases

• If you define a custom initializer in the main struct declaration, the synthesized memberwise initializer is not automatically kept there.
• The memberwise initializer is based on stored properties, not computed properties.
• If all stored properties have default values, Swift can synthesize both a memberwise initializer and a no-argument default initializer.
• Access control can make the synthesized initializer less visible than expected, especially in reusable modules.
• For public library APIs, relying on a synthesized memberwise initializer is often not ideal because property changes can change the initializer signature.
• Classes do not get the same kind of automatic memberwise initializer synthesis that structs do.
• If a property uses a constant declaration with let, it still participates in the memberwise initializer, but it must be initialized exactly once.

9. Practical Mini Project

Let’s build a small but complete example using memberwise initializers for a shopping cart item model. The goal is to show a struct with required properties, default values, and an extra custom initializer added in an extension.

struct CartItem {
    let name: String
    let price: Double
    var quantity: Int = 1
    var isTaxable: Bool = true

    func totalPrice() -> Double {
        return price * Double(quantity)
    }
}

extension CartItem {
    init(freeItemNamed name: String) {
        self.name = name
        self.price = 0.0
        self.quantity = 1
        self.isTaxable = false
    }
}

let coffee = CartItem(name: "Coffee", price: 4.5, quantity: 2)
let sticker = CartItem(freeItemNamed: "Promo Sticker")

print(coffee.totalPrice())
print(sticker.totalPrice())

9.0
0.0

This mini project shows several useful ideas together. The main struct body gets a synthesized memberwise initializer. The default values make some arguments optional at the call site. The extension adds another initializer without removing the memberwise one. This is a very practical pattern for lightweight models.

10. Key Points

• A memberwise initializer is automatically synthesized for many Swift structs.
• It creates one parameter for each stored property.
• Default property values can make some initializer arguments optional.
• A no-argument initializer only exists when every stored property has a default value.
• Writing a custom initializer in the struct body removes the synthesized memberwise initializer there.
• Adding custom initializers in an extension can preserve the synthesized memberwise initializer.
• For public APIs or validated construction, explicit initializers are usually better.

11. Practice Exercise

Practice what you learned by creating a struct named Movie.

• Add stored properties for title, year, and rating.
• Give rating a default value of 0.0.
• Create one instance using the synthesized memberwise initializer with all values.
• Create another instance that uses the default rating.
• Print both movie titles and ratings.

Expected output: Two printed lines showing each movie title and its rating.

Hint: Because rating has a default value, you should be able to omit it in one initializer call.

struct Movie {
    let title: String
    let year: Int
    var rating: Double = 0.0
}

let movie1 = Movie(title: "The Journey", year: 2024, rating: 8.7)
let movie2 = Movie(title: "Untitled Story", year: 2025)

print("\(movie1.title): \(movie1.rating)")
print("\(movie2.title): \(movie2.rating)")

The Journey: 8.7
Untitled Story: 0.0

12. Final Summary

Swift struct memberwise initializers are one of the language's most useful convenience features for custom types. They let you create instances by passing values that match the struct's stored properties, which reduces boilerplate and keeps your code easy to read. For plain data models, they are often the simplest and clearest way to construct instances.

You also saw the important rules around defaults, custom initializers, extensions, and access control. The biggest beginner traps are assuming that every struct gets a no-argument initializer, and forgetting that a custom initializer in the struct body removes the synthesized memberwise initializer there. Once you understand those rules, memberwise initializers become very predictable.

A good next step is to learn how custom initializers differ between struct and class, including designated and convenience initializers, so you can choose the right construction pattern for each kind of Swift type.