What is an RC File?

📋 On This Page

What is RC? Quick Facts What It Declares What It Looks Like From Script to Program RC vs RES How to Open Getting the Icons Editing an RC File Are RC Files Safe? FAQ

📖 What is an RC File?

An RC file is a Windows resource script. It is a plain text file where a developer lists the parts of a program that are not code, the icon, the menus, the dialogs and the on screen text.

Think of it as a parts list for the look of a program. Some entries name a separate file, an icon here, a bitmap there. Others describe the item in full, a menu laid out line by line. The script gathers all of it in one readable place.

On its own an .rc does nothing. It is a source file, written to be fed to a compiler that turns it into the binary the program actually uses. What follows is what it declares, how it names the icons and how to read one.

⚡ Quick Facts

Full Name	Windows Resource Script
Extension	.rc
Developer	Microsoft
Category	Resource script, source file
Format	Plain text
Written by	A developer, by hand or in Visual Studio
Compiles to	A binary .res file
Declares	Icons, menus, dialogs, strings
Related Formats	RES, ICO, EXE, DLL

📦 What an RC File Declares

Each line in an .rc names a resource and gives it an ID the program can call up. The entries fall into two camps:

🔗 Ones that name a file
Icons, cursors and bitmaps point at a separate file on disk. The script holds the name, not the picture.

📄 Ones written inline
Menus, dialogs and string tables are spelled out in the script itself, line by line.

That split matters for anyone after the artwork. The icon is never in the .rc. The script only tells you which file to go and find.

👀 What an RC File Looks Like

Because it is text, you can read an .rc straight off. A short one might look like this:

IDI_APPICON  ICON    "app.ico"
IDB_LOGO     BITMAP  "logo.bmp"

IDR_MAINMENU MENU
BEGIN
    POPUP "File"
    BEGIN
        MENUITEM "Exit", ID_EXIT
    END
END

The first two lines name outside files, the .ico and the bitmap. The menu below is written out in place. One glance tells you the program's icon is a file called app.ico, sitting next to the script.

🔧 From Script to Program

The .rc is the first step of a short chain that ends in a working program:

.rc script

You are here, plain text

→

rc.exe

The Resource Compiler

→

.res file

Compiled, binary

→

.exe or .dll

Finished, icons inside

The Resource Compiler reads the script, pulls in every file it names and packs the lot into a binary .res file. The linker then folds that .res into the program. By the end, the icon named in one line of your script is riding inside the finished .exe.

💡 Where it fits: The .rc is the human end of the chain. It is the only file here you can open and read like a document, which is why it is the place to look when you want to know what a program is built from.

⚖️ RC vs RES

These two are the same job at two stages, the script and its compiled form. If both sit in a folder, this is the difference:

Feature	RC	RES
Form	Plain text you can read	Binary you cannot
Role	The source script	The compiled output
Holds the art	No, it names the files	Yes, the art is inside
Written by	A developer	The Resource Compiler
Order	Comes first	Built from the .rc

✅ Good to know: To read an icon you want the compiled side, not the script. The RES file guide covers the binary that actually carries the artwork, and it is the file an icon tool opens.

📂 How to Open an RC File

An .rc is text, so opening it is easy. What you reach for depends on whether you want to read it or work on it:

✅ Just to Read It

Open the .rc in any text editor, Notepad works fine.
Scan for the ICON lines to see which icons it names.
Note the .ico file names it points at.

🧰 Other Routes

Visual Studio: shows the resources visually and as text.
A code editor: adds syntax colour for easier reading.
A resource editor: edits the entries with a front end.
Not the ICO Converter: a .rc is text, so open the files it names instead.

🖼️ Getting the Icons

Since the .rc holds no artwork, getting an icon means following where the script points:

📤 Two Ways to the Icon

Read the ICON lines and open the named .ico files directly.
Or if the project is built, open the compiled .res or the finished .exe.
Feed any of those to the Univik ICO Converter and export as ICO or PNG.

📚 The Compiled Side

Once the script is built, the icon it named lives in the .res and the program. Reading it out of an EXE or DLL is walked through in full here, and the same tool opens the .res.

✏️ Editing an RC File

Because the script is text, you can change it in any editor, renaming resources, swapping an icon file or adjusting a menu. A caveat comes with that freedom.

⚠️ An edit is not the end: Changing the .rc does nothing to a program that is already built. The Resource Compiler has to rebuild the .res, and the program has to be linked again, before your change shows up. Editing the script alone leaves an existing .exe untouched.

🔒 Are RC Files Safe?

An .rc is plain text and runs nothing, so opening one to read it carries no risk. It is a source file, the same kind of thing as any code you might view in an editor.

✅ The usual care: Give a script from an unknown project the same caution you would any source you did not write, since it names file paths and can pull in other files at build time. Reading it, though, is safe.

❓ Frequently Asked Questions

An RC file is a Windows resource script. It is a plain text file where a developer lists an application's resources, the icon, the menus, the dialogs and the text, either naming an outside file or spelling out the resource inline. The Resource Compiler turns it into a binary .res.

An .rc is what a developer writes, a .res is what the compiler makes from it. The .rc is readable text that lists the resources and points at the icon files by name. The Resource Compiler reads it and produces the binary .res. So the .rc is the source you edit and the .res is the output you do not.

An .rc is plain text, so any text editor opens it, Notepad included. A developer would open it in Visual Studio, which shows the resources visually as well as in text. Reading the file tells you which icon and image files the project uses and by what name.

No. An .rc names its icons rather than holding them. A line like IDI_ICON1 ICON "app.ico" points at a separate .ico file on disk. The actual icon lives in that .ico, then in the compiled .res and the finished program, not in the script.

Read the .rc to find the ICON lines and the .ico file names they point at, then open those .ico files. If the project is already built, the same icons sit in the compiled .res and the finished .exe, and the Univik ICO Converter reads either one.

A developer writes it, either by hand in an editor or through the resource designer in Visual Studio, which saves the layout back to the .rc as text. It is a source file, so it is authored rather than generated by a build.

Yes, since it is text. You can change resource names, IDs and the files it points at in any editor. A change only reaches the program after the Resource Compiler rebuilds the .res and the program is linked again, so editing the script alone does not alter an existing .exe.

An .rc is plain text and runs nothing, so opening one to read it is safe. Treat it like any source file. The only caution is ordinary care with a script from an unknown project, since it names file paths and includes other files during the build.