The universal address for network resources

One path.
Everywhere.

Universal Naming Convention gives people and programs a consistent way to find shared files, folders, and devices across a network.

Analyze or convert a path →Fix a connection ↓
NETWORK PATHUNC
\\SERVER\SHARE\PATH
Host computerShared resourceOptional location

01 / ANALYZE + CONVERT

Paste a path.
Know exactly what it is.

Validate a network path, separate its components, catch common problems, and translate it into the format your next tool expects.

Syntax only, not a connectivity test. Processing runs in this page; data-handling details.

TYPEUNC path
STATUSValid structure
SERVERfileserver
SHAREteam

✓Structure checked only. Server existence, permissions, and application support are not tested.

Choose your destination

8 translations
Canonical UNC\\fileserver\team\projects\2026\plan.docx

Paste into File Explorer or an application that accepts Windows network paths.

File URIfile://fileserver/team/projects/2026/plan.docx

Spaces and Unicode are percent-encoded. Browser and application security rules may prevent opening file links.

SMB URIsmb://fileserver/team/projects/2026/plan.docx

For SMB-aware file managers such as macOS Connect to Server. This is not an HTTPS link.

PowerShell'\\fileserver\team\projects\2026\plan.docx'

Single-quoted literal: backslashes remain unchanged; embedded apostrophes are doubled. Use -LiteralPath where available.

JSON string"\\\\fileserver\\team\\projects\\2026\\plan.docx"

A JSON string literal: every backslash is escaped. A JSON parser restores the original path.

C# verbatim@"\\fileserver\team\projects\2026\plan.docx"

Verbatim string literal for C# source code, not for Explorer.

Python"\\\\fileserver\\team\\projects\\2026\\plan.docx"

An ordinary quoted Python string with escaped backslashes. The path still requires OS/network access.

Slash notation//fileserver/team/projects/2026/plan.docx

A textual representation only. It is not automatically a mounted filesystem path on Linux or macOS.

02 / GUIDED TROUBLESHOOTING

Find the layer.
Then the fix.

Separate syntax, connectivity, identity and permissions. This guide never probes your network. Commands run only if you choose to use them on your own authorized computer.

Reference: Microsoft TCP diagnostics · DNS lookup · Logon-session mappings

CHECK 1 OF 2

Check the address and network

Replace this example with your approved server and share. Try the share root in File Explorer, without the nested filename. Connect to your organization’s network or approved VPN first.

\\fileserver\team

Example commands, not results from your computer. Replace example names before running.

Still stuck? Give your IT team the exact error, affected path, time, account context and which check failed. Redact sensitive names before sharing publicly.

03 / COPY-READY EXAMPLES

Use it in
the real world.

PowerShell
Test-Path '\\server\share\folder'
Command Prompt
dir \\server\share\folder
Map a drive
net use Z: \\server\share
Python
from pathlib import Path
path = Path(r'\\server\share\file.txt')
C#
var path = @"\\server\share\file.txt";
Group Policy
\\domain.example\SYSVOL\domain.example\Policies
DFS namespace
\\domain.example\Departments\Finance
Administrative share
\\workstation-07\C$\Windows

04 / THE STANDARD

A location that
speaks for itself.

Unlike a mapped drive letter, a UNC path doesn’t depend on how one computer is configured. It names the host and share directly, making it portable, explicit, and automation-friendly.

\\SERVER\SHARE\PATH
01

Prefix

\\

Two backslashes signal that the location is a network resource.

02

Server

SERVER

The hostname or IP address of the computer providing the resource.

03

Share

SHARE

The published name of the shared folder, printer, or device.

04

Path

PATH

Optional folders and a filename inside the share.

05 / A SHORT HISTORY

Born on the LAN.
Still at work.

UNC emerged with the first generation of PC local-area networking: a direct, machine-independent way to name a resource without relying on a locally assigned drive letter.

1980s

The network becomes a place

As PC networks and the LAN Manager protocol family took shape, shared resources needed addresses that worked from any connected machine. The familiar \\server\share form supplied that common language.

1990s

Windows makes it everyday

Windows networking and SMB/CIFS brought UNC paths into offices at scale—for shared folders, printers, logon scripts, home directories, and administrative shares.

2000s

From one server to a namespace

Active Directory and Distributed File System made domain-based paths practical. A stable UNC name could point people to data even as the servers behind it changed.

Today

A durable convention

Modern Windows APIs still recognize the two-backslash form, while SMB 2 and 3 carry it across contemporary enterprise, NAS, and hybrid environments.

Technical references: Microsoft UNC specification ↗IETF file URI history ↗

06 / QUICK REFERENCE

Patterns worth
remembering.

UNC is most common on Windows and SMB networks, but the naming idea is broader: identify the authority first, then the resource.

01Shared folder\\atlas\projects
02Nested file\\atlas\projects\briefs\launch.docx
03Administrative share\\workstation-07\C$\Windows

Use backslashes

Windows UNC paths use \, not the forward slash used in web addresses.

Permissions still apply

A correctly formed path identifies a resource; it does not grant access to it.

Names beat drive letters

\\server\share remains clear when Z: means something different elsewhere.

GUIDE 01

UNC paths vs. mapped drives

Why the same resource can have two addresses—and which one belongs in automation.

Read guide →GUIDE 02

UNC path length explained

Classic limits, extended-length syntax, and the practical rules that matter today.

Read guide →GUIDE 03

How to open a UNC path

Windows Explorer, Run, Command Prompt, PowerShell, and common cross-platform options.

Read guide →