File extension check: record complete names in Windows 11

A file extension check makes the ending of a filename visible so you can compare it with an expected format. With Windows 11 and three ready, harmless files you already know, this exercise produces a saved and reopened observation note, not a conversion or a security verdict.

Updated: 2026-10-18

What does a file extension check actually establish?

A folder may contain a report, an image and a spreadsheet with familiar names. If Windows hides their endings, those names can conceal a useful distinction: the item you expect to be an Excel workbook may have a different suffix. Before changing anything, reveal the complete names and record what you see. This is a small observation task, not an investigation of an unknown download.

An extension is the part after the final period in a filename, such as pdf in monthly-report.pdf. Microsoft explains that extensions help Windows associate files with applications and icons. The association is useful, but it does not inspect the contents. A filename is not independent evidence that the contents are genuine, readable or safe.

The outcome here is deliberately limited. You will compare three observed endings with three expectations that existed before the inspection. You will save discrepancies without pretending to resolve them. There is no requirement to open the practice files, rename them or prepare a delivery package. Only the observation note needs to be saved and reopened.

This differs from document version approval evidence. That exercise asks whether approval refers to the intended document state. A filename ending neither proves approval nor identifies which wording was accepted. Keep those questions separate even when both arise in the same folder.

Prepare three known files and independent expectations

Use your own non-confidential files whose origins you understand. A PDF report you saved, a PNG image you exported and a workbook you created are suitable possibilities. Keep the originals unchanged. Do not download sample executables or use a suspicious attachment to make the exercise more interesting. That would introduce a different task and risk without improving this check.

Write the expected format before revealing the suffix. The expectation should come from a known export choice or an established requirement. “I need the workbook in xlsx” is a useful input. “It has an Excel-looking icon” is not an independent format requirement. If you only know that an item is a picture, do not invent a PNG requirement.

Have Windows 11, File Explorer and an available text editor ready. With three prepared files, this narrow task is intended for a short fifteen-minute session. That is a conditional planning target, not a measured user trial. If the files or their expected formats are not ready, preparation is a legitimate stopping point.

The worked examples below are constructed teaching material. They do not describe Anar's computer, a client incident or an observed performance improvement. Use the example to understand the comparison, then substitute the names you actually inspect. Missing observations should remain missing rather than being completed from the sample.

• Choose three known harmless files without modifying them.
• Record each expected format and where that expectation came from.
• Identify the folder well enough to return to the same items.
• Leave an unknown expectation unresolved instead of guessing.

Reveal the complete names in File Explorer

Open File Explorer from the taskbar and navigate to the folder containing your selected items. In Windows 11, select View > Show > File name extensions. This is the route described in Microsoft's extension and File Explorer documentation. Look at a known file and check that its ending is now visible. Do not record success merely because you clicked a menu item.

The nearby Hidden items setting does something different: it shows hidden files and folders. You do not need to change it for this exercise. Making extensions visible does not mean that every hidden object is now displayed, and showing hidden items does not by itself establish that complete filename endings are visible.

If a long name is cut off, adjust the view or name-column width until you can read the ending. Do not reconstruct the missing characters from memory. An unreadable complete name should be recorded as an unresolved observation. That is more useful than a confident statement based on the portion you happened to see.

Copy the first full name into your note, including its periods and ending. Repeat for the other two items. Do not double-click an unfamiliar item to discover what it is. An unexpected suffix is a reason to preserve the observation and stop, not permission to experiment with opening it.

If the instructions do not match your interface, record the Windows version and the menu you can see. Keep the observation pending until you can identify the applicable route. This guide is scoped to Windows 11; it does not present a Windows 10 path or make a promise about every managed workplace configuration.

Compare the suffix without pretending to convert the file

Read each expectation beside the complete name you observed. If the ending matches, use a limited result: “filename suffix matches the stated requirement”. Avoid “file validated”, which suggests you inspected more than its name. The following example deliberately includes a mismatch so that a saved note can preserve an unresolved result.

These are fictional names and supplied observations, not records of an actual desktop test. The third row does not establish corruption. A CSV can hold tabular information, but it does not have the requested xlsx ending. The requirement may need clarification, or the wrong output may have been selected. This observation alone cannot decide which explanation is correct.

A name can contain several periods. In report.final.pdf, final is part of the base name and pdf is the ending. Record the entire name, then the ending separately. Do not use words such as final or approved inside a name as substitutes for either a format check or approval evidence.

Do not fix the mismatch by replacing csv with xlsx in the name. Microsoft explicitly distinguishes changing an extension from converting a file. If another format is genuinely required, the appropriate application's supported save or export route becomes a separate task. This article does not instruct you to run that conversion or claim its success.

When an expectation was never established, write “expected format unresolved”. Matching an observed suffix to a requirement invented after seeing it would make the comparison meaningless. A useful record preserves both uncertainty and the reason for it.

Save the observation note and reopen the exact file

Open Start, search for Notepad and select the application. Create a new text note and copy the template below. Fill it with the full names you actually read. A private folder path may contain a person's name; there is no need to send this note to anyone or publish that path. Keep the exercise local.

Task: Windows 11 filename-extension observation
Date and inspected folder:
1. Expected format and source of requirement:
   Complete filename / observed suffix / result:
2. Expected format and source of requirement:
   Complete filename / observed suffix / result:
3. Expected format and source of requirement:
   Complete filename / observed suffix / result:
Unresolved issue and next action:
Not checked: contents, safety, authenticity or conversion.

In Notepad, choose File > Save As. Select Documents, enter file-extension-check.txt and save the note. If a note with that name already exists, add a date to the base name instead of overwriting it. Keep the txt ending for this text note. Do not rename any of the three original practice files.

Close this note document, then locate the saved txt in Documents and reopen that exact note with Notepad. Check that all three entries and the unresolved-issue line remain present. Return to the original folder in File Explorer and compare the complete names with the reopened record. The output is the stored record, not just text left in an unsaved editor tab.

If a line is missing, complete the note, save it and repeat the reopening check. If Notepad is unavailable, leave the save-and-reopen stage pending rather than claiming another application's workflow was tested. Throughout this process, the original files should remain unchanged. No archive, upload or recipient test is needed.

Keep observation, acceptance and sharing separate

You now have a small record linking each known file to an expectation and an observed ending. It can expose a simple mismatch before a larger workflow begins. It cannot tell you whether the report contains the correct figures, the picture meets a quality requirement or the workbook calculates correctly. Those questions need their own checks.

For content analysis, the document review guide compares an extracted answer with the source. That is different from observing a suffix. The image preparation guide concerns how an image is presented and delivered on a website; seeing png in a name does not complete that work.

If a later job involves several files in an archive, use the ZIP delivery acceptance exercise. It compares expected paths with extracted files and checks readability. Do not expand this filename exercise into a duplicate archive manifest. Likewise, recipient access testing establishes whether another person can perform the required reading, commenting or editing action. A visible extension proves none of those permissions.

Finish with an honest sentence: “I recorded the visible suffixes of three known files; one mismatch remains unresolved.” Change the count only to reflect your own observations. This is a useful result precisely because it does not disguise incomplete checks as a general declaration that the files are ready or safe.