PowerShell Write to Log File | Create Log File In PowerShell

Logging is a critical component of any scripting or programming environment, including PowerShell. It allows administrators and developers to keep track of what their scripts are doing, catch errors, and debug issues. In this post, we’ll explore various methods to write to log files in PowerShell, providing examples and complete scripts to help you implement logging in your PowerShell tasks.

To write to a log file in PowerShell, you can use built-in cmdlets like Out-File or Add-Content to append text to a file, or Start-Transcript to capture a session transcript. For more control, create a custom logging function that includes timestamps and custom messages. For advanced logging, consider using the PSFramework module for features like log rotation and levels.

Why Logging Matters in PowerShell

Logging is the process of recording events and data to a file or other output streams. In PowerShell, logging is vital for debugging purposes, monitoring script execution, and ensuring that you have a record of what actions were taken and when.

There are various ways you can create a log file in PowerShell.

Method 1: Start-Transcript and Stop-Transcript

PowerShell offers a built-in cmdlet called Start-Transcript to log a PowerShell session. This cmdlet starts recording all interactions with the console and saves them to a specified file. To stop recording, use the Stop-Transcript cmdlet.

Here is an example.

Start-Transcript -Path "C:\Logs\PowerShell_Log.txt"
# Your script commands here

Once you execute the above PowerShell script, it will create a log file and write the particular text in the above specified path.

Method 2: Out-File Cmdlet

The Out-File cmdlet in PowerShell is another way to write output directly to a log file. You can use it to append or overwrite data in a log file.

Here is a complete example:

"Information: Logging started." | Out-File -FilePath "C:\Logs\ScriptLog.txt" -Append
# Your script commands here
"Information: Logging completed." | Out-File -FilePath "C:\Logs\ScriptLog.txt" -Append

This method allows you to selectively log information to your file, providing more control over what gets logged.

Method 3: Add-Content Cmdlet

Add-Content is a cmdlet in PowerShell that lets you append content to a log file without overwriting the existing content. This is useful for adding log entries as your script runs.

Here is a complete example.

Add-Content -Path "C:\Logs\ScriptLog.txt" -Value "Script has started at $(Get-Date)"
# Your script commands here
Add-Content -Path "C:\Logs\ScriptLog.txt" -Value "Script has finished at $(Get-Date)"

This cmdlet is similar to Out-File -Append, but it’s specifically designed for adding text to files, making it ideal for logging purposes.

Method 4: Custom Logging Function

You can create a custom function to handle logging in PowerShell. This function can include parameters for the log message, log file path, and other options like timestamping.

Here’s a simple function that writes log entries to a specified file:

function Write-Log {
    Param (
    Add-Content -Path $LogFile -Value $LogString

# Usage
$LogFile = "C:\MyFolder\script.log"
Write-Log "This is a log entry" -LogFile $LogFile

This function uses the Add-Content cmdlet to append the log string to the specified log file.

You can see the output in the screenshot below after I executed the PowerShell script using VS code.

Create Log File In PowerShell

To include timestamps in your logs in PowerShell, you can modify the Write-Log function as follows:

function Write-Log {
    param (
    $timestamp = Get-Date -Format "yyyy-MM-dd HH:mm:ss"
    $logEntry = "$timestamp - $Message"
    Add-Content -Path $LogPath -Value $logEntry

$LogPath = "C:\MyFolder\CustomLog.txt"
Write-Log -LogPath $LogPath -Message "Script started"
# Your script commands here
Write-Log -LogPath $LogPath -Message "Script ended"

This will prepend the current date and time to each log entry, formatted as YYYY-MM-DD HH:MM:SS.

Method 5: PSFramework

For more advanced logging in PowerShell, you can use the PSFramework module. It provides a robust logging solution with features like log rotation, levels, and component-based logging.

Here is a complete example.

Import-Module PSFramework
Set-PSFLoggingProvider -Name logfile -Enabled $true -LogPath "C:\Logs\PSFrameworkLog.txt"
Write-PSFMessage "Script started" -Level Important
# Your script commands here
Write-PSFMessage "Script ended" -Level Important

This method requires the installation of the PSFramework module but offers a professional logging setup that can be essential for enterprise-level scripts.

Best Practices for PowerShell Logging

When implementing logging in PowerShell, consider the following best practices:

  1. Consistency: Use a consistent log file naming convention to make it easier to locate and analyze logs.
  2. Timestamps: Include timestamps in your logs to provide context for when events occurred.
  3. Log Levels: Implement log levels (e.g., DEBUG, INFO, WARN, ERROR) to categorize the importance of log messages.
  4. Error Handling: Include logging within try/catch blocks to capture exceptions and errors.
  5. Log Rotation: Implement log rotation to prevent log files from becoming too large and unmanageable.
  6. Sensitive Data: Be cautious about logging sensitive information. Always sanitize logs if they may contain passwords, PII, or other sensitive data.


PowerShell provides several methods for creating and writing to a log file. You can use the PowerShell built-in cmdlets like Start-Transcript and Out-File, or you’re creating a custom logging function. For more complex scenarios, you can also use external modules like PSFramework.

I hope that now, from this tutorial, you can create and write a log file in PowerShell using the above-mentioned methods.

You may also like: