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.

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.

TYPEUNC path
STATUSValid structure
SERVERfileserver
SHAREteam

The path has a valid UNC structure.

Ready in every format

8 translations
Canonical UNC\\fileserver\team\projects\2026\plan.docx
File URIfile://fileserver/team/projects/2026/plan.docx
SMB URIsmb://fileserver/team/projects/2026/plan.docx
PowerShell'\\fileserver\team\projects\2026\plan.docx'
JSON string"\\\\fileserver\\team\\projects\\2026\\plan.docx"
C# verbatim@"\\fileserver\team\projects\2026\plan.docx"
Python"\\\\fileserver\\team\\projects\\2026\\plan.docx"
POSIX-style//fileserver/team/projects/2026/plan.docx

02 / 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.

03 / 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.

04 / TROUBLESHOOT

When the path
doesn’t connect.

Choose the symptom that best matches what you see. Start at the top—the checks are ordered from common to less common.

The server or share cannot be found

  1. Confirm the server and share names are spelled correctly.
  2. Try the server’s IP address to separate DNS trouble from SMB trouble.
  3. Make sure you are on the organization’s network or VPN.
  4. Verify SMB file sharing is running and reachable on TCP port 445.

05 / 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

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.