.pl File Extension

What kind of file is a .pl?

A .pl file most often contains a Perl program, but the suffix is ambiguous. Prolog projects also traditionally use .pl for source code. SWI-Prolog explicitly documents this conflict and accepts .pl alongside alternatives such as .pro.¹ Both forms are editable text, not compiled executables.

There are no fixed magic bytes. A first line such as #!/usr/bin/perl strongly suggests Perl, while Prolog directives often begin with :-. Neither clue is guaranteed, so inspect the project, syntax, and documentation before choosing an interpreter. IANA does not register a Perl- or Prolog-specific media type; Poly classifies .pl as readable text/plain.²

How do I open a .pl on my computer?

Any text editor can open .pl on Windows, macOS, or Linux. Visual Studio Code, Vim, Neovim, and other programming editors can provide language-aware highlighting after you select Perl or Prolog.

For a known Perl program, install Perl and pass the file to the interpreter:

perl report.pl

Perl also supports directly executable scripts on systems that honor a #! line.³ For Prolog, open or load the file with the implementation used by its project. SWI-Prolog loads .pl files directly.¹

Viewing a .pl file as text does not run it. Do not execute an unfamiliar file merely to identify it. Perl's -c option checks syntax, but it can still run BEGIN, UNITCHECK, and CHECK blocks and load modules, so it is not a safe sandbox for untrusted code.³

Poly support for .pl

Poly opens .pl as source text in a read-only, code-friendly viewer with word wrap and in-file search. It indexes the readable content for exact and semantic search, so you can find named routines, predicates, comments, or code by its purpose.

The Poly agent can summarize the file, explain functions or predicates, and help identify whether the syntax looks like Perl or Prolog. Poly does not execute the program, load dependencies, or reproduce interpreter state. Because the suffix is ambiguous, confirm the language before relying on language-specific advice.

History of .pl

The suffix belongs to two long-running programming traditions. Perl 1.000 was released on December 18, 1987, and .pl became a familiar convention for Perl programs.⁴ Perl modules normally use .pm, which helps distinguish reusable modules from program files and older .pl libraries.⁵

Prolog software also adopted .pl for source. Modern SWI-Prolog still recommends it when there is no operating-system association conflict, while suggesting .pro where a single global association would otherwise clash with Perl.¹ The filename alone therefore cannot settle which language a file contains.

Working with .pl and alternatives

Use project context and a few textual clues before editing or running the file:

Keep the existing suffix when a project's tools and scripts expect it. If Perl source contains non-ASCII text, record its encoding; Perl's use utf8; pragma tells the parser to treat source text as UTF-8.⁶ Changing .pl to .pm or .pro does not restructure code or guarantee compatibility. A real migration requires updating imports, build rules, launch commands, and file associations.