This question already has an answer here:

In PowerShell is there an equivalent of touch?

For instance in Linux I can create a new empty file by invoking:

touch filename

On Windows this is pretty awkward -- usually I just open a new instance of notepad and save an empty file.

So is there a programmatic way in PowerShell to do this?

I am not looking to exactly match behaviour of touch, but just to find the simplest possible equivalent for creating empty files.

marked as duplicate by phuclv, Pimp Juice IT, Dave M, music2myear, Mokubai Sep 22 '17 at 8:13

This question has been asked before and already has an answer. If those answers do not fully address your question, please ask a new question.

  • 1
  • Thanks. I looked at them, but most of the answer focus on command-prompt. I'd like to have a PowerShell solution that doesn't require me to install new applications. – jsalonen Nov 7 '12 at 19:33
  • Downvoted the question - both features are only a few more lines of code, just implement both, not just half, esp. when the missing half other command is so dangerous. – yzorg Feb 18 '14 at 0:49
  • @yzorg: What do you mean by both features? I was only asking how to create an empty file in PS the way you can do with touch in Linux. – jsalonen Feb 18 '14 at 9:13
  • @jsalonen Use *nix touch on an existing file it will update the last write time without modifying the file, see the links from @amiregelz. This question has a high google ranking for powershell touch, I wanted to alert copy/paste-ers that just this half of it can destroy data, when *nix touch doesn't. See @LittleBoyLost answer that handles when the file already exists. – yzorg Feb 18 '14 at 14:44

14 Answers 14


Using the append redirector ">>" resolves the issue where an existing file is deleted:

echo $null >> filename
  • 3
    Also known as 'echo null>filename' from a command prompt, possibly a batch file. Cool to see the PowerShell version of it, thanks! – Mark Allen Nov 7 '12 at 21:11
  • 16
    touch is rather different than this if the file already exists – jk. Nov 7 '12 at 22:46
  • 8
    echo is unnecessary, $null > filename works great. – alirobe May 30 '15 at 12:54
  • 6
    This writes 2 bytes of unicode BOM 0xFEFF for me. – mlt Apr 20 '16 at 19:08
  • 4
    Important note: Many unix tools don't deal with BOM. This includes git for example(even on windows). You're gonna have problems if you use files created in this manner with tools that don't recognize BOMs. e.g. you try to create your .gitignore using this command and wonder why it won't work. BOM is the reason. – martixy Jul 31 '17 at 22:21

To create a blank file:

New-Item -ItemType file example.txt

To update the timestamp of a file:

(gci example.txt).LastWriteTime = Get-Date
  • 4
    I think this is the best approach! – Jayesh Bhoot Nov 4 '13 at 15:30
  • Does this work for updating the timestamp of a folder? – riahc3 Jul 28 '15 at 6:31
  • 1
    @riahc3, use this: (gi MyFolder).LastWriteTime = Get-Date . You could use that for files too. – dangph Jul 28 '15 at 11:26
  • 8
    Even more pithy: ni example.txt – Nick Cox Dec 21 '17 at 1:03
  • 1
    This method doesn't add the awful BOM bytes and the encoding happily appears to be UTF-8. – Davos Mar 26 '18 at 10:33

Here is a version that creates a new file if it does not exist or updates the timestamp if it does exist.

Function Touch-File
    $file = $args[0]
    if($file -eq $null) {
        throw "No filename supplied"

    if(Test-Path $file)
        (Get-ChildItem $file).LastWriteTime = Get-Date
        echo $null > $file
  • 4
    This is the correct answer for replicating the Unix touch program (albeit with a different name), but the question is oriented to simply creating a new file. – Jamie Schembri Jan 4 '14 at 11:59
  • 11
    Very, very tiny quibble: While Touch-File conforms to the Verb-Noun naming convention of PS, Touch is not an "approved" verb (not that it's a significant requirement: msdn.microsoft.com/en-us/library/ms714428.aspx). File is fine, btw. I recommend the names Set-File or Set-LastWriteTime or, my favorite, Update-File. Also, I would recommend Add-Content $file $null instead of echo $null > $file. Finally, set an alias with Set-Alias touch Update-File if you want to keep using the command touch – Alan McBee May 25 '17 at 23:36

In PowerShell you can create a similar Touch function as such:

function touch {set-content -Path ($args[0]) -Value ($null)} 


touch myfile.txt


  • This is great, thanks! Just what I wanted! Any ideas how I could install this function into the PowerShell so that it loads automatically when I start the shell? – jsalonen Nov 7 '12 at 19:34
  • 2
    Add it to your $profile file. (Run notepad $profile to edit that file.) – Mark Allen Nov 7 '12 at 21:12
  • 24
    This will delete the contents of the file if it exists. – dangph Jan 24 '13 at 6:31
  • 1
    Or the safe version that does not clear out existing file contents function touch { if((Test-Path -Path ($args[0])) -eq $false) { set-content -Path ($args[0]) -Value ($null) } } – alastairtree Sep 11 '18 at 16:51

I prefer

fc > filename

for this task. To work with non-empty files you can use

fc >> filename

fc is simply an alias for Format-Custom. I chose it because it is a short command that does nothing in this context, a noop. It is also nice because if you forget the redirect

fc filename

instead of giving you an error, again it just does nothing. Some other aliases that will work are

ft -> Format-Table
fw -> Format-Wide

I put together various sources, and wound up with the following, which met my needs. I needed to set the write date of a DLL that was built on a machine in a different timezone:

$update = get-date
Set-ItemProperty -Path $dllPath -Name LastWriteTime -Value $update

Of course, you can also set it for multiple files:

Get-ChildItem *.dll | Set-ItemProperty -Name LastWriteTime -Value $update
  • 1
    +1 for the most Powershell-ish way to change LastWriteTime on a file (which is what I needed), though the question focused on the new file creation feature of the touch command. – Nathan Hartley Feb 25 '13 at 15:20
  • Without using a variable? – riahc3 Jul 28 '15 at 6:33

There are a bunch of worthy answers already, but I quite like the alias of New-Item which is just: ni

You can also forgo the file type declaration (which I assume is implicit when an extension is added), so to create a javascript file with the name of 'x' in my current directory I can simply write:

ni x.js

3 chars quicker than touch!

  • This is not idempotent ni : The file 'x.js' already exists – Steven Penny Nov 30 '17 at 12:43

Open your profile file:

notepad $profile

Add the following line:

function touch {New-Item "$args" -ItemType File}

Save it and reload your $profile in order to use it straight away. (No need to close and open powershell)

. $profile

To add a new file in the current directory type:

touch testfile.txt

To add a new file inside 'myfolder' directory type:

touch myfolder\testfile.txt

If a file with the same name already exists, it won't be overidden. Instead you'll get an error.

I hope it helps

Bonus tip:

You can make the equivalent of 'mkdir' adding the following line:

function mkdir {New-Item "$args" -ItemType Directory} 

Same use:

mkdir testfolder
mkdir testfolder\testsubfolder
ac file.txt $null

Won't delete the file contents but it won't update the date either.


It looks like a bunch of the answers here don't account for file encoding.

I just ran into this problem, for various other reasons, but

echo $null > $file

$null > $file

both produce a UTF-16-LE file, while

New-Item $file -type file

produces a UTF-8 file.

For whatever reason fc > $file and fc >> $file, also seem to produce UTF-8 files.

Out-File $file -encoding utf8

gives you a UTF-8-BOM file, while

Out-File $file -encoding ascii

gives you a UTF-8 file. Other valid (but untested) encodings that Out-File supports are: [[-Encoding] {unknown | string | unicode | bigendianunicode | utf8 | utf7 | utf32 | ascii | default | oem}]. You can also pipe stuff to Out-File to give the file some text data to store, and also an -append flag. For example:

echo $null | Out-File .\stuff.txt -Encoding ascii -Append

this example does not update the timestamp for some reason, but this one does:

echo foo | Out-File .\stuff.txt -Encoding ascii -Append

Although it does have the side effect of appending "foo" to the end of the file.

If you are unsure about what encoding you have, I've found VS-Code has a nifty feature where at the bottom right hand corner it says what the encoding is. I think Notepad++ also has a similar feature.


For the scenario you described (when the file doesn't exist), this is quick and easy:

PS> sc example.txt $null

However, the other common use of touch is to update the file's timestamp. If you try to use my sc example that way, it will erase the contents of the file.

  • 1
    Thanks! What does sc mean? Edit: figured it out ("Set Content") – jsalonen Feb 27 '13 at 15:00

to create an empty file in windows, the fastes way is the following:

fsutil file createnew file.name 0

The zero is filesize in bytes, so this is also useful to create large file (they will not be useful for testing compression since they do not contain actual data and will compress down to pretty much nothing)


The webpage http://xahlee.info/powershell/PowerShell_for_unixer.html suggests:

new-item -type file [filename]

and this does indeed create a new file of size zero.

This doesn't perform the other function of Unix touch, namely to update the timestamp if filename already exists, but the question implies that the user just wants to create a zero-sized file interactively without resorting to Notepad.


I used the name "Write-File" because "Touch" isn't an approved PowerShell verb. I still alias it as touch, however.


  Creates a new file or updates the modified date of an existing file.

 .Parameter Path
  The path of the file to create or update.
Function Write-File {
       [Parameter( Mandatory=$True, Position=1 )]
       [string] $Path,
       [switch] $WhatIf,
       [System.Management.Automation.PSCredential] $Credential
    $UseVerbose = $PSCmdlet.MyInvocation.BoundParameters['Verbose'].IsPresent -eq $True
    $UseDebug = $PSCmdlet.MyInvocation.BoundParameters['Debug'].IsPresent -eq $True
    $TimeStamp = Get-Date
    If( -Not [System.Management.Automation.WildcardPattern]::ContainsWildcardCharacters( $Path ) ) {
        New-Item -ItemType:File -Verbose:$UseVerbose -Debug:$UseDebug -WhatIf:$WhatIf -Credential $Credential -Path $Path -ErrorAction SilentlyContinue -Confirm:$False | Out-Null
    Set-ItemProperty -Verbose:$UseVerbose -Debug:$UseDebug -WhatIf:$WhatIf -Credential $Credential -Path $Path -Name LastWriteTime -Value:$TimeStamp -Confirm:$False | Out-Null

Set-Alias -Name touch -Value Write-File

Export-ModuleMember -Function Write-File
Export-ModuleMember -Alias touch


Import-Module ./Touch.psm1
touch foo.txt


  • Paths in other directories
  • Credential for network paths
  • Verbose, Debug, and WhatIf flags
  • wildcards (timestamp update only)
  • The New-Item command has been offered in four previous answers.  You have provided a 20-line wrapper for it.  Can you explain a bit more clearly what advantage your solution has over the earlier ones?  For example, what are these Verbose, Debug, and WhatIf flags, etc? – Scott Mar 23 '17 at 4:08
  • One important difference between this answer and New-Item is that this updates the timestamp of existing files. – jpaugh Jul 26 '18 at 15:49

Not the answer you're looking for? Browse other questions tagged or ask your own question.