You are currently viewing Naming Exports So You Can Find Them Later

Naming Exports So You Can Find Them Later

TL;DR: Name an export with the date, the tool, the operation, and enough of the input to tell siblings apart. Do not call it output.txt. A name that states what the file is will outlast the tab you copied it from.

The default name is a delay, not a label

Converters and calculators hand you a result and let the browser call the download “download,” “output,” or the tool’s slogan. Those names collide the moment you convert a second file. They also say nothing in a search six weeks later, when you need the Base64 of the logo and not the Base64 of the icon. Rename before you move on to the next task. Renaming later, in a folder of twelve “output (3).txt” files, requires opening each one.

Masters Tool pages cover encoding, color, code formatting, and calculations. The export may be a download, a copy to the clipboard, or a screenshot. The naming rule is the same. A clipboard paste still needs a filename the moment it lands in your notes or your repo. Decide the name, then paste into a file that already has that name, rather than pasting into Untitled and hoping.

A pattern that sorts itself

Use a stable order: date, project, operation, distinguishing input. 2026-10-08_site-header_png-to-base64_logo.txt tells you when, which job, what happened, and which source. ISO dates sort chronologically in a normal file listing. The operation sits in the middle so a search for “base64” or “hex” finds the right family. The source basename at the end separates the logo from the social icon you converted the same day.

Avoid spaces if the file will be used in a terminal or a URL. Avoid calling two different operations by the same verb. “Converted” might mean entities, Base64, or a unit change. Use the specific word. Avoid “final,” “final2,” and “new.” They are not operations. If you must mark a revision, use r2, r3, and keep r1. Overwriting the only copy of r1 is how a teammate’s integration breaks with no explanation.

What to put in the name, and what to put in the first line

The filename cannot hold every option. Charset, whether a data-URL prefix was included, the unit pair, the rounding: those belong in the first line inside the file, as a comment the next tool can ignore or as a header you strip before use. The filename holds enough to choose the right file without opening it. The first line holds enough to repeat the operation. If you skip the first line, the filename will grow into a paragraph and then get truncated by a sync tool.

For a calculation that is not a file, the “export” might be a note. Give the note a title with the same pattern, and put the inputs in the body. A note called “calc” is the same failure as output.txt. A note called “2026-10-08 porch slab cubic meters” is a file you can find. Include the unit in the title whenever two unit systems are in play. A bare number in a title will be reused in the wrong system.

Pairs and folders

  • Keep source and export together only if the names pair. logo.png beside logo.b64.txt is clear. logo.png beside output.txt is a puzzle.
  • Do not use the source extension for the export. A Base64 text file named logo.png will be opened as an image and declared broken.
  • One folder per batch date if you will run the job again. Do not pour October into September’s folder.
  • Skip secret names. If the source filename contains a client name you should not spread, use a neutral code in the export name and keep a private mapping.

Cloud sync and chat apps rewrite names too. They may replace characters, add “ (1),” or strip a leading dot. After you upload, look at the name that arrived. If the channel mangled it, send a zip whose internal names you control, or paste the text into the repository yourself.

Names and the tools that read them

Some formatters and minifiers assume the extension tells them the language. A JavaScript snippet saved as .txt may not be highlighted or linted. A CSV of unit conversions saved as .html will open in the wrong place. Choose the extension for the consumer of the file, and keep the operation in the basename. prices.converted.csv can still open as a spreadsheet. prices-converted with no extension will open as a mystery.

If a page offers a download button and a copy button, prefer copy into a file you named, when the result is text. Downloads land in a global folder you share with every other site, and they arrive with the page’s default name. Clipboard-to-named-file is an extra step and a cleaner archive.

Make the first rename the habit

The next time a result appears, pause before the next tool. Name the file. Write one option line inside it. Then continue. The pause is shorter than the archaeology you will otherwise do on a Thursday.

Generate the result from the right page on the Masters Tool homepage, and store it under a name that states the operation. The hub will not remember what you downloaded. The filename is the memory.