Convert Int to String in Swift: 5 Fatal Mistakes Beginners Make

Online Python Trainer for Beginners

Learn Python easily without overwhelming theory. Solve practical tasks with automatic checking, get hints in Russian, and write code directly in your browser — no installation required.

Start Course

Convert Int to String in Swift: Top Mistakes and How to Avoid Them

Have you ever caught yourself thinking: “Why is it so hard to turn a simple number into a string in Swift?” Spoiler: it’s actually quite simple. But it’s this very simplicity that throws the most unexpected pitfalls at developers (especially beginners). On Stack Overflow, the question “Convert Int to String in Swift” gathers thousands of views, and beneath it — dozens of comments with typical mistakes.

In this article, we’ll break down the 5 most common mistakes when converting Int to String. You’ll learn how String(describing:) works, why string interpolation in SwiftUI can be dangerous, and why your code might “crash” at the worst possible moment. We won’t just show you the correct code — we’ll explain why it’s correct. Let’s go!

Why Convert Int to String Isn’t Just “Do It and Done”?

Swift is a strictly typed language. The compiler doesn’t tolerate liberties, and that’s great. However, when you write "Number: " + 42, the compiler throws an error: Cannot convert value of type 'Int' to expected argument type 'String'. And that’s where the fun begins.

Converting Int to String is a basic operation, but it hides pitfalls: from choosing the wrong method to implicit performance issues. Let’s examine each mistake under a microscope.

Mistake #1: Using `String(describing:)` for Int

Many beginners, upon seeing String(describing:), think: “Oh, a universal method! It will turn anything into a string.” And that’s true, but with a catch.

let number = 42let stringValue = String(describing: number)print(stringValue) // "42"

At first glance — it works. But let’s dig deeper. String(describing:) is intended for debugging. It calls the CustomStringConvertible protocol. For Int, this does return the number. But for Optional, things get sad:

let optionalNumber: Int? = 42let stringValue = String(describing: optionalNumber)print(stringValue) // "Optional(42)" — most likely not what you wanted!

You’ll get the string "Optional(42)", not "42". If this value ends up in the UI — the user will see strange text. If in a log — you’ll get confused during analysis.

How to do it correctly?

Use String(init:) — this is a direct initializer specifically designed for numeric types:

let number = 42let stringValue = String(number)print(stringValue) // "42" — clean and clear

// For optionals — use optional binding:let optionalNumber: Int? = 42if let number = optionalNumber {    let stringValue = String(number)    print(stringValue) // "42"}

Mistake #2: Blind Faith in String Interpolation

String interpolation is a powerful tool: "\(number)". But many think it’s the safest way to convert. And it almost is, but there’s a “but”.

let count = 5let message = "You have \(count) new messages"// "You have 5 new messages" — great!

The problem arises when you use interpolation inside complex expressions or with optionals:

let optionalCount: Int? = nillet message = "You have \(optionalCount) new messages"// "You have nil new messages" — terrible!

In Swift 5 and later, interpolation for optionals became smarter (using StringInterpolation), but if you’re working with older code or haven’t updated Xcode — expect surprises.