What is the RIS file format?
A .ris file contains information about cited publications or references to them, saved in text format developed by Research Information Systems in the early 1990s. The format was created to standardize data exchange between various citation software tools and is now widely associated with Clarivate and EndNote. It uses human-readable syntax and can be opened using any text editor. A single .ris file can hold information about one or more publications. Each publication referenced in .ris files must be tagged using two required tags:
TY- type of publication,ER- end of record, signaling the transition to the next publication.
The format is based around a 6-character structure for each new line. The first two characters define the type of field (tag), the next two are space characters, followed by a hyphen and a space. Each line must end with MS Windows newline characters - CR and LF. There are various types of tags used in .ris files, for example:
AU,A1,A2,A3,A4- authors of the given publication,AB- an abstract,L1,L2,L3- various types of links,SP,EP- start and end page numbers,TI,T1,T2,T3,TT- titles,VL- volume number,Y1,Y2- dates.
Some tags are constrained by length limits or the type of data they may hold, but there are no restrictions on tag order. For types of publications, the shortcuts listed in the specification can be used - such as JOUR for journal article or BOOK for a monograph. Many applications and systems use .ris citation files, including digital libraries and library catalogues. The format is closely related to .BIB (BibTeX) and .ENW (EndNote export), which serve similar purposes in academic workflows.
Security & safety
RISK: LOWRIS files are plain text metadata - no code, no macros, effectively zero direct risk. The only practical concerns are hygiene-level: a URL field could point anywhere (reference managers don't auto-open them), and citation files from untrusted sources may simply contain wrong or spammy metadata. Safe to open in any text editor.
Format details
in a nutshellPrograms that open RIS files
Technical details
deep spec| File type | Plain-text tagged bibliographic format; fully human-readable with no binary sections |
| Tag structure | Each tag is two uppercase ASCII letters followed by two spaces, a hyphen, and a space (e.g., `TY - `, `AU - `) |
| Mandatory record start | Every record must open with the `TY` tag specifying the reference type (e.g., `TY - JOUR`) as the very first field |
| Record terminator | Each record closes with `ER - ` on its own line; a blank line typically follows before the next record |
| Line endings | Specification requires Windows-style CRLF line endings; modern parsers generally accept Unix LF-only as well |
| MIME type | `application/x-research-info-systems` |
| Reference type codes | Over 40 standardized `TY` values including `JOUR` (journal article), `BOOK` (book), `CONF` (conference paper), `THES` (thesis), `CHAP` (book chapter), `RPRT` (report) |
| Author fields | Multiple author tags supported - `AU`, `A1` (primary), `A2` (secondary), `A3` (tertiary), `A4` (subsidiary); one author per tag line |
| Multi-record support | A single `.ris` file may contain any number of reference records, each delimited by its own `TY`/`ER` pair |
| Tag ordering | No mandatory order for tags within a record, except `TY` must appear first and `ER` must appear last |
| URL and link fields | `L1` stores a local file path or URL, `L2` a full-text URL, `L3` a related URL; all three may appear multiple times per record |
| Date representation | Dates stored in `Y1` and `Y2` tags using the pattern `YYYY/MM/DD/other`; month, day, and the free-text fourth component are optional |
| Abstract continuation | The `AB` tag supports multi-line abstracts; continuation lines begin with six leading space characters per the original specification |
| File identification | No magic bytes or binary header; files are identified by the `TY - ` content pattern at the start of the first record |
| Character encoding | Original specification assumed ASCII/ANSI; current implementations commonly export and import UTF-8 to support non-Latin scripts |
| Interoperability | Native import/export supported by EndNote, Zotero, Mendeley, JabRef, Web of Science, PubMed, Google Scholar, and most institutional repositories |
| Released | Early 1990s (Reference Manager, Research Information Systems); publicly documented tag set, no formal standards body |
| Open standard | Yes · royalty-free |
| Specification | en.wikipedia.org |