Note: The function is also available as an MIT-licensed Gist, and only it will be maintained going forward. Source code of function Out-FileUtf8NoBom: The function below improves on this only slightly: all input objects are still buffered first, but their string representations are then generated and written to the output file one by one.Dudley's own answer requires that the entire file contents be built up in memory first, which can be problematic with large files. Generally, though, this technique is not advisable for 2 reasons: (a) the whole file must fit into memory and (b) if the command is interrupted, data will be lost. This is necessary in order to be able to write back to the same file (update it in place). Note how (Get-Content $MyPath) is enclosed in (.), which ensures that the entire file is opened, read in full, and closed before sending the result through the pipeline. an additional -UseLF switch allows you transform Windows-style CRLF newlines to Unix-style LF-only newlines.Įxample: (Get-Content $MyPath) | Out-FileUtf8NoBom $MyPath # Add -UseLF for Unix newlines.input objects that aren't strings are formatted as they would be if you sent them to the console, just like with Out-File.

you can use it just like Out-File in a pipeline.Dudley's own simple and pragmatic answer (and ForNeVeR's more concise reformulation):įor convenience, here's advanced function Out-FileUtf8NoBom, a pipeline-based alternative that mimics Out-File, which means: If you're running Windows 10 and you're willing to switch to BOM-less UTF-8 encoding system-wide - which can have side effects - even Windows PowerShell can be made to use BOM-less UTF-8 consistently - see this answer. In other words: If you're using PowerShell version 6 or higher, you get BOM-less UTF-8 files by default (which you can also explicitly request with -Encoding utf8 / -Encoding utf8NoBOM, whereas you get with-BOM encoding with -utf8BOM). Note: This answer applies to Windows PowerShell by contrast, in the cross-platform PowerShell Core edition (v6+), UTF-8 without BOM is the default encoding, across all cmdlets.

System text encoding utf8