Print GMT Time Using Excel VBA

VBA & macros · Updated November 2, 2026

To print the current GMT time with Excel VBA on Windows, call the Windows GetSystemTime API and send its result to the VBA Immediate window with Debug.Print. The code below reports the computer’s current UTC time, including milliseconds; UTC is the precise modern time standard often casually called GMT.

VBA code to print the current UTC time

In Excel for Microsoft 365 on Windows, open the Visual Basic Editor, insert a standard module, and paste this code. The first macro prints a timestamp to the Immediate window. The second writes a timestamp into the currently selected worksheet cell instead. Save a copy of the workbook before running either macro: VBA changes cannot be reversed with Ctrl+Z.

Option Explicit

' Windows SYSTEMTIME structure, whose fields are 16-bit values.
Private Type SYSTEMTIME
    wYear As Integer
    wMonth As Integer
    wDayOfWeek As Integer
    wDay As Integer
    wHour As Integer
    wMinute As Integer
    wSecond As Integer
    wMilliseconds As Integer
End Type

' PtrSafe supports 64-bit Office as well as 32-bit Office with VBA7.
Private Declare PtrSafe Sub GetSystemTime Lib "kernel32" _
    (ByRef lpSystemTime As SYSTEMTIME)

Public Sub PrintUtcTime()
    Dim utc As SYSTEMTIME
    Dim stamp As Date

    ' Save a copy first; macros cannot be undone with Ctrl+Z.
    GetSystemTime utc
    stamp = DateSerial(utc.wYear, utc.wMonth, utc.wDay) + _
            TimeSerial(utc.wHour, utc.wMinute, utc.wSecond)

    Debug.Print Format$(stamp, "yyyy-mm-dd hh:nn:ss") & "." & _
                Format$(utc.wMilliseconds, "000") & " UTC"
End Sub

Public Sub WriteUtcTimeToActiveCell()
    Dim utc As SYSTEMTIME
    Dim stamp As Date

    ' Select the destination cell before running this macro.
    GetSystemTime utc
    stamp = DateSerial(utc.wYear, utc.wMonth, utc.wDay) + _
            TimeSerial(utc.wHour, utc.wMinute, utc.wSecond)

    With ActiveCell
        .Value = stamp
        .NumberFormat = "yyyy-mm-dd hh:mm:ss ""UTC"""
    End With
End Sub

The first routine produces a value like 2026-11-02 18:42:07.035 UTC; the date and time in that example are illustrative, not a guaranteed reading. The actual output depends on the computer clock when you run the macro. The worksheet routine writes the date and time to the selected cell and displays a UTC label, but stores whole-second precision.

Where the output appears and how to run it

In Excel on Windows, press Alt+F11 to open the Visual Basic Editor. In the editor, choose Insert > Module and paste the code into the new module. Save the file as an Excel Macro-Enabled Workbook (.xlsm) if you need to keep the VBA project. To run the immediate-window version, open View > Immediate Window in the editor, click inside PrintUtcTime, and press F5. The output appears in the Immediate window, not in a worksheet cell and not on a physical printer.

To put the timestamp on a sheet, return to Excel, select the cell you want to use, then run WriteUtcTimeToActiveCell from the editor. It overwrites the selected cell, so confirm that the cell is empty or that replacing its contents is intended. To make a paper copy, use this worksheet option and then print the sheet through Excel; Debug.Print is a diagnostic output command, not a printer command.

On a Mac, the Visual Basic Editor may be opened with Option+F11; some keyboards require Fn as well. However, the Windows API declaration in this example depends on kernel32 and will not run in Excel for Mac. Excel for the web cannot run VBA macros. Those platforms need a different, platform-specific way to obtain UTC.

Why the code uses GetSystemTime

Windows keeps system time in UTC and provides GetSystemTime to retrieve it as separate year, month, day, hour, minute, second, and millisecond fields. The VBA declaration tells Excel how to call that Windows function, and the SYSTEMTIME type describes the structure of the values it returns. The code combines the calendar date and clock time into a VBA date value for readable formatting.

This approach asks Windows for UTC directly. It does not first read local time and then try to infer the computer’s time zone. Consequently, the displayed result does not change merely because the Windows time-zone setting or daylight-saving status changes. Its accuracy still depends on the system clock: the API does not contact a time server or independently verify that the computer’s clock is correct.

The declaration uses PtrSafe, which is appropriate for current 32-bit and 64-bit Office installations that use VBA7. The structure uses VBA Integer fields because the Windows structure contains 16-bit values. The returned year, month, day, and time fields fit within the range of that VBA type.

GMT, UTC, and what Excel stores

GMT means Greenwich Mean Time and is historically tied to mean solar time at Greenwich. UTC, Coordinated Universal Time, is the modern international time standard used for precise timekeeping. In everyday conversation and many business systems, people use “GMT” to mean a zero-offset time, but UTC is the more accurate label for a computer timestamp. The macro labels its output UTC for that reason.

Excel date-and-time values do not carry a time-zone identifier. A date written into a cell is a serial value, not a complete time-zone-aware timestamp. Excel cannot tell from the underlying value alone whether it represents UTC, Pacific time, or another zone. The worksheet macro appends the text UTC in the cell’s number format to make the intended interpretation visible. Keep that label if the value is shared or compared with local times.

For the same reason, a timestamp that looks correct in a cell can still be misunderstood by another application or person if its time zone is undocumented. For exported data, use a clear heading such as “Timestamp (UTC)” and a consistent format such as year-month-day followed by a 24-hour clock. If a system needs an explicit machine-readable zone, use an export format that supports one rather than assuming Excel’s serial value contains it.

Why Now and Time do not print GMT

VBA’s Now function returns the current date and time according to the computer’s local settings; Time returns the local clock time. Formatting either value with the letters “GMT” or “UTC” only changes its appearance. It does not convert the value or make it a UTC reading. For example, assigning Now to a cell and applying a UTC label can create a misleading timestamp whenever the computer is not set to UTC.

That distinction matters in files used across regions. A local clock can move forward or backward when daylight-saving rules change, and different locations observe different rules. Simply subtracting a fixed number of hours is not a general conversion method: the offset can vary by date and location. Reading UTC directly avoids that conversion problem when the task is to record the current UTC instant.

The direct API approach is not a replacement for converting an existing timestamp from a known local time zone. To convert a past or future local date correctly, you need to know the source time zone and apply its rules for the date in question. The computer’s current offset alone is not enough to infer historical or future daylight-saving transitions reliably.

One-time timestamps versus a live clock

Running either macro captures a timestamp once. The cell value does not continue to tick, and the Immediate window does not refresh itself. That is usually desirable for a log entry, report creation time, or record of when a macro ran: the value stays fixed after the event.

A live clock is a different requirement. It needs repeated updates, for example through a scheduled VBA procedure or a worksheet formula that recalculates. Repeatedly changing a cell can interfere with user edits, trigger other workbook events, or make a printed report inconsistent. Decide whether you need a permanent event timestamp or a changing display before automating refreshes.

If the goal is to log an event, write the UTC value once when that event occurs, ideally alongside a description or record identifier. If users need to see both UTC and local time, store or display them as separate, clearly labeled values. Do not silently reinterpret a UTC serial value as local time just by changing its number format.

Common errors and practical checks

  • “Sub or Function not defined” or a declaration error: Confirm that the API declaration and SYSTEMTIME type are in the same standard module as the macros. Do not paste the declaration inside a procedure or into a worksheet cell.
  • “Can’t find project or library” or a missing DLL error: This code is for Windows. The library name kernel32 is a Windows component and is not available in Excel for Mac or Excel for the web.
  • No visible result: Debug.Print writes to the Immediate window in the Visual Basic Editor. Open it using View > Immediate Window; the timestamp will not appear in a sheet unless you run the cell-writing macro.
  • A cell gets replaced: The worksheet version writes to ActiveCell. Select a safe destination first, or change the code to refer to a specific worksheet and range that exist in your workbook.
  • The clock is wrong: GetSystemTime reads Windows’ current system clock. Check Windows date, time, and synchronization settings if the result is inaccurate; the macro itself does not correct the clock.
  • The output appears to be local time: Check the code and label rather than changing the number format. This API returns UTC, but later code or an export process might convert, relabel, or interpret the value differently.

Before enabling macros, use a workbook and VBA code you trust. You do not need to lower Excel’s overall macro security settings just to use a personal macro-enabled file. If the workbook is shared, explain that the timestamp is UTC and identify which cell or column contains it.

Alternatives and platform limits

For a Windows-only workbook, GetSystemTime is a direct option because Windows exposes the UTC clock through this API. If a workbook must run on both Windows and Mac, avoid assuming that a Windows DLL declaration will work everywhere. A cross-platform solution needs an implementation for each operating system or an external source designed to provide UTC; the right choice depends on whether the workbook can use platform-specific code or network services.

For a simple display rather than a VBA task, a dedicated clock or a time service may be more appropriate, but it should be clear whether its value is live, cached, or refreshed. A worksheet formula based on local date-and-time functions does not by itself turn local time into UTC. Whatever alternative you choose, test the output, document the time zone, and distinguish a captured timestamp from a value that updates.

Frequently Asked Questions

Does Debug.Print print the time on paper? No. It writes text to the Immediate window in the Visual Basic Editor. Write the value to a worksheet cell if you want to print it from Excel.

Does this macro work in 64-bit Excel? Yes, on Windows with VBA7. The declaration uses PtrSafe, and the Windows SYSTEMTIME fields are represented with the appropriate 16-bit VBA type.

Can I use the code in Excel for Mac? Not as written. It calls the Windows-only kernel32 API. Mac Excel requires a different implementation, and Excel for the web does not execute VBA.

Will the worksheet timestamp update automatically? No. The macro writes a fixed timestamp when you run it. Run it again to replace the value with a new reading; a live clock requires a separate refresh design.

Is GMT exactly the same as UTC? They are often used interchangeably in everyday software and business contexts to mean zero-offset time, but UTC is the modern standard. Labeling the output UTC is clearer for computer-generated timestamps.

Related

Try it: the Column Letter to Number: aA is 27, XFD is 16,384. Converts both ways.

More in VBA & macros

Sources: Function behaviour and menu paths: Microsoft Support documentation for Excel. Method & sources

Spotted an error in this guide? Let us know.