.uris File Extension
.uris file contains, how to open URI lists safely, how Poly handles them, and when another bookmark format is a better fit. File extension details for .uris
Storage Only| File type | URI list |
|---|---|
| MIME type | |
| Encoding | Line-oriented text, with CRLF endings specified by RFC 2483 |
| Operating systems | Windows, macOS, Linux |
| Opens with | Visual Studio Code, Notepad, TextEdit, Other text editors |
| Poly support | Storage only. Poly safely stores, syncs, shares, and versions standalone .uris files. |
| Indexed by Poly | Partial. Poly makes .uris files searchable by filename and basic properties, but not by the URI lines inside. |
| Preview in Poly | No. Download a .uris file and inspect it in a trusted text editor. |
| Poly agent | No. The Poly agent cannot read the contents of a standalone .uris file. |
What kind of file is a .uris?
A .uris file is a plain-text list of Uniform Resource Identifiers. It normally uses the text/uri-list MIME type. Each non-comment line contains one complete URI, while a line beginning with # is a comment. The specification calls for CRLF line endings and does not define a magic number.1
# Project references
https://example.com/specification
https://example.com/implementation#setup
urn:isbn:9780131103627
The plural suffix is meaningful: one file can contain several references. A URL is one kind of URI, but entries may also use urn:, mailto:, file:, or application-specific schemes.2
# character starts a comment only when it is the first character on a line. In https://example.com/guide#setup, it is part of the URI.How do I open a .uris on my computer?
Open a trusted .uris file with a text editor such as Notepad on Windows, TextEdit in plain-text mode on macOS, or a desktop editor on Linux. Visual Studio Code and similar cross-platform editors also make it easy to inspect individual lines.
Do not expect double-clicking to open every destination. Operating systems and browsers may not register .uris as a standalone document type even though web drag-and-drop APIs commonly carry links as text/uri-list data.3 Copy a known http: or https: entry into a browser, or use software that explicitly imports URI lists.
Poly support for .uris
Poly stores, syncs, shares, versions, and finds .uris files by name and basic properties. It does not currently parse a standalone .uris file into bookmarks, preview its destinations, index the URI lines, or give those contents to the Poly agent.
Poly bookmarks are richer when each bookmark has one destination. Create them through Bookmarks, or split a multi-entry .uris file into separate bookmarks when you want destination previews, page-aware search, and agent access. Availability still depends on the destination and its access controls.
History of .uris
The IETF URN Working Group developed text/uri-list for automatically processing lists returned by URI resolution services. Its registration was submitted in April 1997, and RFC 2483 published the format in January 1999.1 The RFC recommends .uris or .uri as filename extensions and describes the intended usage as limited.1
The format later found a practical role in web drag and drop. The HTML standard maps the URL drag-data alias to text/uri-list and returns the first URI when that alias is read.3 That browser behavior concerns typed drag data, not necessarily downloaded .uris files.
Working with .uris and alternatives
Choose a representation based on the task:
| Format | Best use | Important difference |
|---|---|---|
.uris | Machine-readable lists of URI references | One URI per line; supports comments |
.uri | The same URI-list format | Singular alternative suffix |
.url | One Windows desktop internet shortcut | INI-style structure |
.webloc | One macOS internet location | Property-list structure |
| CSV | Links with titles, owners, or status | Explicit columns rather than URI-list syntax |
Renaming a .url, .webloc, or CSV file to .uris does not convert it. Extract each intended destination and write one valid URI per line. Preserve percent-encoding, query strings, and fragments unless you deliberately mean to change the reference.2
Footnotes
- Internet Engineering Task Force. RFC 2483: URI Resolution Services Necessary for URN Resolution. Section 5 defines the syntax, records the 1997 registration, recommends
.urisand.uri, and states that no magic number is assigned. ↩ ↩2 ↩3 - Internet Engineering Task Force. RFC 3986: Uniform Resource Identifier Generic Syntax. The standard defines URI syntax, components, comparison, and security considerations. ↩ ↩2
- WHATWG. HTML Standard: Drag and Drop. The standard defines typed drag data and maps the
URLalias totext/uri-list. ↩ ↩2