Use a filename as a visible conversion recipe
Filename Actions interprets supported commands in an image's filename and applies a local transformation recipe. It is useful when you want an explicit, compact instruction such as resize, re-encode without copied metadata or choose an output format. Select one supported still image and inspect the parsed plan before running it. The name is an instruction to review, not an unrestricted command executed by a shell.
Examples include photo.jpg.nometa, photo.jpg.1920, photo.png.jpg and IMG_8472.heic.1920.nometa.jpg. These examples describe different intentions. A numeric suffix requests a resize bound, nometa requests the supported metadata-removing re-encode behavior, and a format suffix selects a genuine output representation. Simply changing a file's extension outside the tool would not perform those operations.
Read the plan instead of guessing from the punctuation
The editable filename-plan field lets you inspect and adjust the intended recipe. Read the displayed interpretation after a change. A filename may contain ordinary dots as well as action-like parts, and you should not assume that a familiar word was accepted as a supported command merely because it appears in the input.
Keep the recipe simple enough to explain. A resize instruction and an explicit output format can be useful together. A long chain of contradictory suffixes is harder to review and does not create a more powerful workflow. Invalid or unsupported plans should remain errors rather than being silently treated as completed transformations.
This is a single-image tool, not a directory automation system or a way to execute arbitrary code. For folders, Batch Converter offers its own explicit import, output and export stages. For a conventional one-image interface, Convert Image or Resize Image may be easier to review.
The operation order is deliberate
The recipe applies resizing, re-encoding without copied metadata and then a bounded quality search where requested and supported. Understanding that sequence helps explain the result. A smaller grid can reduce how many bytes the encoder needs; a size target does not independently restore detail lost by a preceding resize.
A filename target such as 2mb is a bounded search request, not a guarantee of an exact file length. The result depends on image content, format, permitted quality and dimensions. Read the receipt and actual measured bytes rather than assuming a number in the name proves success.
A resize command also needs context. A small original cannot gain genuine source detail by being represented at a larger size, and a technical screenshot can lose legibility if reduced too far. Inspect the content that matters, not just whether the output dimensions resemble the requested plan.
Formats depend on real decoder and encoder support
Supported still-image inputs include JPEG, PNG, WebP, AVIF, GIF, BMP, TIFF and native HEIC/HEIF within the applicable path's limits. Actual signatures and format features determine admission. A familiar extension does not guarantee support for every compressed TIFF, animated container or camera-specific structure.
Available output choices are JPEG, PNG, WebP and browser-supported AVIF. A browser's ability to display a format is not proof that it can encode it. Read the actual output type and any unsupported-encoder message. Do not accept a different payload hidden under the requested extension as an equivalent result.
HEIC/HEIF here uses the relevant native path. The dedicated shared HEIC conversion tools have a separate reviewed local fallback. A source working in one of those pages does not expand this filename-driven workflow's decoder scope. Keep the product-specific path clear when diagnosing a refusal.
Metadata removal is a scoped re-encode
Nometa does not mean that every possible private structure in every file has been surgically removed while all other bytes remain unchanged. The workflow creates a new image representation without copying source identifying metadata. Structural output information can still be present, and the source ICC profile is not universally preserved.
Visible information remains in the pixels. A screenshot's account name or a photograph's location clue is not removed by a metadata command. Use an appropriate inspection or redaction tool when disclosure is the concern, and check the actual generated file rather than relying on the word in its name.
Original-preservation and delivery-copy goals should stay separate. Keep a master when capture information, profile handling or exact source bytes matter. A useful re-encoded sharing copy can sit alongside it without being described as an archival or universally high-depth equivalent.
Limits still apply to a short recipe
The configured contract is one file, 20 MiB and twelve megapixels. Filename resize commands can specify bounds up to 16,000 pixels, but the pixel limit and format-specific resource rules still apply. An allowed number in one field does not imply that every width-and-height combination is admissible.
Browser memory and codec behavior can add practical constraints. A compact source can require much larger working buffers after decoding. Do not bypass a rejection by changing the name or treating a shorter instruction as a cheaper source. The file must be read and admitted before the requested conversion can produce useful output.
Creative bytes and paths stay in the browser processing workflow, while application assets still load from the site. The tool does not overwrite the source or automatically recover selected files after a reload. Save the useful result before leaving and keep the receipt associated with the correct output.
Verify the real file and its intended use
Open the downloaded result and check format, dimensions, orientation, transparency and necessary detail. Compare measured bytes with any target the recipe requested. A download starting does not prove a completed save, and a correct filename does not prove that its stated transformation happened.
For richer supported properties, Image Inspector can examine the saved image. For a larger collection with explicit naming and folder controls, use Batch Converter with the required access. Choose a workflow that makes the intention clear enough to review, and return to the original when trying a materially different recipe.