Understanding Java toString() vs String.valueOf(): Usage, Null Handling, and Casting

Preface

In everyday development we often encounter three ways to convert objects to strings, especially the first two; developers tend to pick whichever feels convenient, but each method has its own rationale and appropriate scenarios.

Code Examples

1. Primitive Types

(1) Primitive types do not have a toString() method.

(2) Recommended usage

(3) Cannot cast directly

(1) Cast with (String) is a standard type conversion from Object to String; when using (String) you should first check with instanceof to avoid ClassCastException. The compiler does not warn about this, so use it cautiously.

(3) Cannot force cast

2. Wrapper Types

(1) toString() works

(2) String.valueOf()

It works as well.

(3) Wrapper types also cannot be force‑cast

3. Null Value Issues

(1) toString() throws NullPointerException

(2) String.valueOf() returns the string "null"

(3) Null cast succeeds

Source Code Analysis

toString()

String.valueOf()

String.valueOf() adds a null‑check before calling toString(), preventing NullPointerException.

Summary

1. toString() may throw NullPointerException

All Java objects inherit Object.toString(), but you must ensure the object is not null before invoking it; otherwise a NullPointerException is thrown. Subclasses often override this method.

2. String.valueOf() is recommended

String.valueOf() is safe because it returns the literal string "null" for null references and never throws an exception; it is a static method called on the String class.

3. (String) casting is not recommended

When casting an Object to String, you should first verify the type with instanceof to avoid ClassCastException, as the compiler does not warn about unsafe casts.

Recent Technical Articles

1. Why top programmers avoid "!= null" for null checks?

2. SpringBoot Summary: CommandLineRunner

3. MySQL performance vs MariaDB

4. Interview question: Does a program crash without ThreadLocal?