By Anish Singh Walia, Pankaj Kumar and Vinayak Baranwal SimpleDateFormat formats and parses java.util.Date values using custom pattern strings, and DateFormat provides the abstract base API for locale-aware date and time formatting. Use these APIs when you maintain legacy Java code that still depends on java.util.Date; for new code, prefer DateTimeFormatter from the Java 8+ date/time API because SimpleDateFormat is not thread-safe. This tutorial shows how to use DateFormat and SimpleDateFormat for formatting, parsing, timezone conversion, and locale-specific output. It also covers strict validation with setLenient(false), thread safety workarounds, and a practical migration path to DateTimeFormatter. SimpleDateFormat is the DateFormat subclass that lets you define explicit date/time patterns for formatting and parsing in Java. Use DateFormat when you want style-based, locale-aware output through factory methods, and use SimpleDateFormat when you need exact pattern control such as "dd-MM-yyyy" or "yyyy-MM-dd'T'HH:mm:ssZ". The DateFormat style constants (SHORT, MEDIUM, LONG, FULL) produce locale-appropriate output without requiring you to know the exact regional date order, which is useful for user-facing display strings where the format should follow the user’s locale conventions. Use SimpleDateFormat when the output format is fixed by an external requirement such as an API contract, a log format, or a file naming convention, because those cases require an exact pattern regardless of locale. new Locale(String, String) is deprecated as of Java 19. Use Locale.Builder instead. To format time instead of a date, use DateFormat.getTimeInstance() with the same locale and style parameters. For a broader overview of modern Java date/time APIs, see Java 8 Date, LocalDate, LocalDateTime, Instant and Java 8 Features with Examples. SimpleDateFormat pattern letters map directly to date/time components, and correct pattern selection controls both output format and parse behavior. Repeated pattern letters change width, numeric padding, or text style. These common patterns are useful for logs, APIs, and user-facing dates. To format a Date, create a SimpleDateFormat with a pattern and call .format(date). SimpleDateFormat applies timezone and locale rules from the formatter instance, so set those values explicitly when output must be consistent. To parse a string into Date, create a formatter with the exact input pattern and call .parse(input). If only time is provided, Java uses the epoch date as the date portion. parse() throws ParseException when input does not match the configured pattern, so production code should catch it and log both the raw input and the expected pattern. For exception handling patterns you can reuse across services, see Exception Handling in Java and Java 8 Date, LocalDate, LocalDateTime, Instant. SimpleDateFormat is lenient by default, so invalid values can roll over instead of failing; call setLenient(false) to enforce strict validation. SimpleDateFormat can render the same Date in different timezones by setting a timezone on the formatter before output. A Date object stores only a UTC millisecond count and carries no timezone of its own. Timezone is a formatting concern, not a storage concern; the same Date value produces different human-readable output depending on which timezone the formatter applies. This means setTimeZone() must be called on the formatter before format() is called; setting it afterward has no effect on output already produced. See How to Convert Java Date into Specific TimeZone format for deeper timezone conversion patterns. Timezone bugs often come from confusing stored instants with rendered local time. To produce locale-specific date output such as French month names or German day names, pass a Locale to the SimpleDateFormat constructor. Use the built-in constants, Locale.US, Locale.UK, Locale.FRENCH, Locale.GERMAN, for common regions, or construct a custom locale with Locale.Builder when you need a region not covered by the constants. Locale controls which language is used for text fields such as month names, day names, and AM/PM markers. Pass a Locale as the second constructor argument. If you omit it, SimpleDateFormat calls Locale.getDefault() internally, which binds the formatter to the JVM’s runtime locale, a value that differs between developer machines, CI environments, and production servers running under different OS locale configurations. The same pattern produces different text output by locale. Relying on Locale.getDefault() in a JVM running in a server environment can produce inconsistent output because OS locale settings differ across hosts. Always pass an explicit Locale. SimpleDateFormat mutates internal Calendar and NumberFormat state during parse/format operations. If multiple threads use one instance, these mutable fields can be overwritten mid-operation, which causes race conditions and unpredictable output. In practice this surfaces as dates from one thread appearing in another thread’s result, .parse() returning a completely wrong date with no exception, or an ArrayIndexOutOfBoundsException thrown from inside the formatter itself. These failures are intermittent and load-dependent, which makes them difficult to reproduce in a single-threaded test environment. When you need concurrency-safe formatting in legacy code, isolate instances by thread or request scope. For background on Java threading behavior, see Java Thread Example. ThreadLocal<SimpleDateFormat> gives each thread its own formatter instance and avoids shared mutable state. In thread-pool environments such as servlet containers and Spring applications, threads are reused across requests and are never terminated, which means ThreadLocal values are never automatically removed. Always call FORMATTER.remove() after the operation completes, or the formatter instance will persist for the lifetime of the thread and accumulate as a memory leak under sustained load. DateTimeFormatter is immutable and thread-safe, so one shared static instance is safe. Migration to DateTimeFormatter removes thread-safety risks, eliminates ThreadLocal workarounds, and integrates cleanly with java.time types. For most codebases the migration is mechanical: pattern syntax is nearly identical, the two APIs can coexist during an incremental rollout, and you do not need to convert everything at once. The main risk is the u symbol, which means day-of-week in SimpleDateFormat and year in DateTimeFormatter; patterns copied directly between APIs without checking this will silently produce wrong output. This side-by-side snippet shows equivalent formatting and parsing behavior in legacy and modern APIs. Most pattern letters are similar, but some symbols differ and can break migrations if copied directly. Use this checklist to convert one formatter at a time in existing codebases. DateTimeFormatter works exclusively with java.time types (LocalDate, LocalDateTime, ZonedDateTime, Instant). It does not accept java.util.Date directly. If you have code that still produces java.util.Date values, for example from a legacy ORM or JDBC driver, convert first with date.toInstant() before passing to DateTimeFormatter. The two APIs can coexist in the same codebase during an incremental migration; you do not need to convert everything at once. DateTimeFormatter also replaces ParseException with java.time.format.DateTimeParseException, which is an unchecked exception, so try-catch blocks become optional but are still recommended in production parsing code. For migration context and type choices, refer to Java 8 Date, LocalDate, LocalDateTime, Instant. DateFormat is an abstract class that defines the contract for date/time formatting. SimpleDateFormat is its concrete subclass that allows custom pattern-based formatting. You use SimpleDateFormat directly in code; you use DateFormat as a reference type when you want to accept any implementation. No. SimpleDateFormat instances are not thread-safe. Sharing a single instance across threads without synchronization causes unpredictable parse and format results. Use ThreadLocal<SimpleDateFormat> or replace it with java.time.format.DateTimeFormatter, which is immutable and thread-safe. Instantiate SimpleDateFormat with the pattern "dd-MM-yyyy", then call .parse(yourString). Wrap the call in a try-catch block for ParseException. Ensure the input string matches the pattern exactly, including separator characters. Call .setTimeZone(TimeZone.getTimeZone("America/New_York")) on your SimpleDateFormat instance before calling .format(date). The underlying Date object holds UTC milliseconds; the formatter applies the timezone offset during output. It produces an ISO 8601-compatible timestamp, for example 2024-06-15T14:30:00+0530. The T is a literal character wrapped in single quotes. Z represents the RFC 822 timezone offset. Replace new SimpleDateFormat("yyyy-MM-dd") with DateTimeFormatter.ofPattern("yyyy-MM-dd"). Replace .parse() calls with LocalDate.parse() or LocalDateTime.parse(). Replace .format(date) calls with formatter.format(localDate). Note that DateTimeFormatter uses u for year in some contexts instead of y. By default, SimpleDateFormat uses lenient parsing mode, which adjusts out-of-range values rather than rejecting them. Call .setLenient(false) before parsing to enforce strict validation and throw ParseException on invalid input. Pass the Locale as a second argument to the constructor: new SimpleDateFormat("dd MMMM yyyy", Locale.FRENCH). This renders month and day names in the specified language, which is critical for applications serving multiple regions. This guide covered DateFormat and SimpleDateFormat fundamentals, pattern syntax, formatting and parsing workflows, timezone behavior, locale-aware rendering, thread safety issues, and migration to DateTimeFormatter. You can now choose the right formatter for legacy and modern code, parse input defensively with strict validation, avoid locale and timezone drift in server environments, and remove concurrency risks from shared date formatters. For next steps, review Java 8 Date, LocalDate, LocalDateTime, Instant, Java 8 Features with Examples, Exception Handling in Java, and How to Convert Java Date into Specific TimeZone format to continue modernizing date/time handling in Java applications. Thanks for learning with the DigitalOcean Community. Check out our offerings for compute, storage, networking, and managed databases. Learn more about our products I help Businesses scale with AI x SEO x (authentic) Content that revives traffic and keeps leads flowing | 3,000,000+ Average monthly readers on Medium | Sr Technical Writer(Team Lead) @ DigitalOcean | Ex-Cloud Consultant @ AMEX | Ex-Site Reliability Engineer(DevOps)@Nutanix Java and Python Developer for 20+ years, Open Source Enthusiast, Founder of https://www.askpython.com/, https://www.linuxfordevices.com/, and JournalDev.com (acquired by DigitalOcean). Passionate about writing technical articles and sharing knowledge with others. Love Java, Python, Unix and related technologies. Follow my X @PankajWebDev Building future-ready infrastructure with Linux, Cloud, and DevOps. Full Stack Developer & System Administrator. Technical Writer @ DigitalOcean | GitHub Contributor | Passionate about Docker, PostgreSQL, and Open Source | Exploring NLP & AI-TensorFlow | Nailed over 50+ deployments across production environments. You Should have addressed the important topic like Date conversion to different TimeZones. Anyway great tutorial. Thank you for the article, it’s been very helpful. I believe the day of the week should be amended in this manner below: EEEE, E Day name in the week Tuesday(EEEE), Tue(E or EEE) How can i set date format 20th may, 2010 You Should Append About Calendar Class because Date is deprecated This is the best tutorial on dates I have ever seen Wrong, “whereas DateFormat allows only formatting of Date.” it can be for parse string to Date Please complete your information! Get paid to write technical tutorials and select a tech-focused charity to receive a matching donation. Full documentation for every DigitalOcean product. The Wave has everything you need to know about building a business, from raising funding to marketing your product. Stay up to date by signing up for DigitalOcean’s Infrastructure as a Newsletter. New accounts only. By submitting your email you agree to our Privacy Policy Scale up as you grow — whether you're running one virtual machine or ten thousand. From GPU-powered inference and Kubernetes to managed databases and storage, get everything you need to build, scale, and deploy intelligent applications.