Skip to main content

How to Associate a File Extension with a Program in Batch Script

A file association is the link in Windows that connects a file extension (like .txt) to a specific action, which usually means opening it with a particular program (like Notepad.exe). Being able to control these associations from a script is a powerful tool for administrators and developers, allowing you to set up a consistent environment, fix broken associations, or register a custom file type for your own application.

This guide will teach you how to manage these associations using the two core command-line utilities for this purpose: assoc and ftype. You will learn the essential two-step process required to create a new, working file association from scratch.

The Two-Step Process: assoc and ftype​

Creating a file association from the command line is always a two-step process. You cannot do it with a single command. The two steps are:

  1. assoc: Associate a file extension (.log) with an internal "File Type" name. This File Type is just a descriptive label that you create (e.g., LogFile).
  2. ftype: Assign an open action to that File Type. This is where you specify the executable and the command line used to open the files.

Think of it like this: assoc links an extension to a name, and ftype links that name to a program.

The Core Commands Explained​

assoc (Associate)​

The assoc command is used to view or create the link between an extension and a File Type.

  • assoc .ext: Displays the current association for .ext.
  • assoc .ext=FileType: Creates or changes the association.

ftype (File Type)​

The ftype command is used to view or create the command string that is executed for a given File Type.

  • ftype FileType: Displays the current command for FileType.
  • ftype FileType="path\to\program.exe" "%1": Creates or changes the command.

The "%1" is a crucial placeholder. It represents the full path of the file that was double-clicked. Windows will substitute this into your command string at runtime.

Basic Example: Associating a .log File with Notepad​

Let's create a system-wide association to make all .log files open with Notepad. This requires administrator privileges.

@ECHO OFF
REM This script must be run as an Administrator.

ECHO --- Associating .log files with Notepad ---
ECHO.

ECHO Step 1: Associating the .log extension with a File Type named 'LogFile'.
assoc .log=LogFile

ECHO.
ECHO Step 2: Associating the 'LogFile' type with the Notepad executable.
ftype LogFile=%SystemRoot%\system32\notepad.exe "%1"

ECHO.
ECHO --- Association complete. ---
ECHO You can verify by running:
ECHO   assoc .log
ECHO   ftype LogFile

After running this script, double-clicking any .log file will now open it in Notepad.

How assoc and ftype Work Together​

When you double-click MyFile.log:

  1. Windows looks up the .log extension in the registry (using assoc).
  2. It finds that .log is associated with the File Type LogFile.
  3. Windows then looks up the LogFile type (using ftype).
  4. It finds the command string: %SystemRoot%\system32\notepad.exe "%1".
  5. It substitutes "%1" with the full path to MyFile.log.
  6. The final command executed is: C:\Windows\system32\notepad.exe "C:\Path\To\MyFile.log".

Key assoc and ftype Parameters​

  • assoc .ext: Displays the association for .ext.
  • assoc .ext=: Deletes the association for .ext.
  • ftype FileType: Displays the command for FileType.
  • ftype FileType=: Deletes the command for FileType.
  • "%1": Represents the file being opened.
  • "%*": Represents all parameters. Useful for more complex actions.
  • "%%~1": Can be used in more advanced scenarios inside other scripts, but "%1" is standard for ftype.

Common Pitfalls and How to Solve Them​

Problem: The Script is Not Run as Administrator​

File associations are stored in the HKEY_CLASSES_ROOT section of the Windows Registry, which is a protected system-wide location. Modifying these settings requires elevated privileges.

Example of script with error:

Access is denied.
ERROR: The system was unable to find the specified registry key or value.

Solution: Run as Administrator​

There is no workaround. The batch script must be executed from a command prompt that was "Run as administrator."

Problem: Handling Paths with Spaces​

If the path to your executable contains spaces, you must quote it correctly.

Example of script with error:

REM This will FAIL.
ftype CustomAppFile=C:\My App\run.exe "%1"

Solution: Quote the Executable Path​

The entire command string after the equals sign should be quoted.

REM This is the correct, safe syntax.
ftype CustomAppFile="C:\My App\run.exe" "%1"

Practical Example: A Full Script to Register a Custom File Type​

This script registers a new, custom file extension .abc and associates it with a custom application. This is a typical task for an application installer.

@ECHO OFF
SETLOCAL
REM This script must be run as an Administrator.

REM --- Configuration ---
SET "Extension=.abc"
SET "FileType=CustomABCFile"
SET "FileDesc=ABC Custom Data File"
SET "AppPath=C:\Program Files\MyCoolApp\viewer.exe"

ECHO --- Registering Custom File Type: %Extension% ---
ECHO.

REM Step 0: Check if the application exists.
IF NOT EXIST "%AppPath%" (
    ECHO [ERROR] Application not found at "%AppPath%". Aborting.
    GOTO :End
)

REM Step 1: Create the association between the extension and the File Type.
ECHO Associating %Extension% with %FileType%...
assoc %Extension%=%FileType%

REM Step 2: Create the command action for the File Type.
ECHO Setting open command for %FileType%...
ftype %FileType%="%AppPath%" "%%1"

REM Step 3 (Optional but Recommended): Set a user-friendly description.
REM This uses the REG command to add a description to the File Type.
ECHO Setting file description...
REG ADD "HKEY_CLASSES_ROOT\%FileType%" /ve /d "%FileDesc%" /f > NUL

ECHO.
ECHO [SUCCESS] The %Extension% file type has been registered.

:End
ENDLOCAL

Conclusion​

The assoc and ftype commands are the essential, built-in tools for managing file associations from a batch script. While they require a two-step process, they provide complete control over how file extensions are handled by Windows.

For reliable scripts:

  1. Always run the script as an Administrator.
  2. First, use assoc .ext=FileType to link the extension to a name.
  3. Second, use ftype FileType="C:\Path\To\App.exe" "%1" to link the name to an action.
  4. Remember that "%1" is the crucial placeholder for the file being opened.

By mastering this two-step process, you can automate the configuration of your Windows environment and ensure your custom file types are handled correctly.

Table of Contents