If you have screenshots from several websites, products, projects, or clients, adding the same label one image at a time becomes tedious very quickly. You open one file, edit its information, type the tag, save it, and repeat the process for every screenshot. A free online bulk image tagger solves that repetitive task by applying one set of tags to many images in a single browser session.
The important detail is that “tagging an image” can mean two different things. You can write keywords into the image's metadata, or you can render the label visibly into a new copy of the image. Metadata is clean and keeps the original pixels unchanged, but phone gallery apps do not consistently display imported keywords. A visible label is less subtle because it changes the image, but it can be seen in almost any gallery, file preview, or messaging app.
What is a bulk image tagger?
A bulk image tagger is a tool that applies the same keyword, category, project name, or label to multiple image files at once. Instead of editing each file separately, you select a batch of images, enter the tags once, choose how the tags should be stored, and download the processed copies.
Common uses include:
- Tagging screenshots by website, product, client, or project
- Adding labels such as “reference,” “inspiration,” “to review,” or “approved”
- Organising UI screenshots into categories like checkout, dashboard, login, or landing page
- Marking image sets for research, design audits, content planning, or QA testing
- Adding searchable keywords to a local archive without uploading the images
The word “bulk” refers to the workflow, not to a special image format. The output is still a normal image file that can be opened, copied, backed up, and shared.
What is the best way to tag multiple images online?
The best method depends on whether the tag needs to be searchable by software or visibly readable by a person. For a private image library or desktop cataloguing application, embedded metadata is usually the cleanest choice. For a phone gallery, a client review, or a file that will pass through messaging apps, a visible label is more dependable.
The practical workflow is:
- Select the JPEG, PNG, or WebP images you want to process.
- Add one tag per line, or enter several short tags for the whole batch.
- Choose Embedded metadata when the original pixels and dimensions must stay unchanged.
- Choose Mobile-visible labels when the tag must be visible in iPhone or Android gallery apps.
- Process the batch and download the individual files or a ZIP archive.
- Open one result in the destination gallery before processing a large archive.
This approach gives you a useful choice instead of pretending that every gallery application handles metadata in the same way.
Embedded metadata versus visible image labels
There are two reliable ways to add tags to a batch of images. They solve different problems, so neither one is universally better.
Embedded metadata keeps the image visually unchanged
Embedded metadata stores the keywords inside the image file rather than drawing them over the image. MediaBrew writes XMP subject values to supported JPEG, PNG, and WebP files. The compressed image payload is copied without re-encoding, so the visual pixels remain unchanged.
This is the right option when:
- You want the image to look exactly the same
- A desktop photo manager or DAM system reads XMP keywords
- You are building a searchable archive for later cataloguing
- You want to preserve the original dimensions and visual quality
- You plan to inspect the tags with a metadata viewer or ExifTool
Metadata is not the same as a visible caption. Many mobile gallery applications show camera information, location, date, or their own descriptions, but they are not required to import and display arbitrary XMP keywords. A successful metadata write therefore does not guarantee that a phone gallery will show the tag on screen.
Mobile-visible labels work in almost any gallery
Mobile-visible mode creates a new PNG and renders the tags in a caption strip below the source image. The text becomes part of the image pixels, so the receiving application does not need to understand XMP, EXIF, IPTC, or any other metadata standard.
Use this option when:
- The tag must be readable in Samsung Gallery, Google Photos, or iPhone Photos
- You are sending the image to someone who may not inspect metadata
- You need the label to survive ordinary file previews and image viewers
- You are creating a visual review board or screenshot catalogue
- The image may be opened on an unknown device or operating system
The trade-off is intentional: the output is a new PNG with a visible caption area. The original file is not overwritten, but the mobile-visible result is not a pixel-identical copy of the source.
Will image tags appear in iPhone and Android galleries?
Not reliably if the tags exist only as embedded keywords. Gallery apps control their own user interface and decide which metadata fields they import, index, or show. A file can contain correct XMP keywords while the gallery displays no visible tag at all.
For the highest chance of consistent visibility on phones, use a label rendered into the image itself. This works because the gallery only has to display the image; it does not have to support a particular metadata field.
On iPhone, the Photos app has its own captions and search behaviour. On Android, Samsung Gallery and Google Photos also have their own tagging, caption, and search features. Those app-level records are not the same as metadata embedded in a downloaded image, and a browser tool cannot create a native album or native gallery database entry from a file alone.
The simple rule is:
- Need a clean original image? Use embedded metadata.
- Need the tag visible everywhere? Use a mobile-visible label.
- Need both? Create the visible copy and keep the original or metadata copy separately.
Does tagging an image change its quality?
Embedded metadata mode does not re-encode the compressed image payload, so it is designed to preserve the source image data while adding the XMP packet. Mobile-visible mode must create a new PNG because it draws the caption into the output. PNG is lossless, but the image dimensions become taller because space is added for the label.
The visible label is therefore not a watermark hidden in metadata. It is part of the actual image. This makes it robust across devices, but it also means you should keep the original files if you may later need an unmodified version.
Can I tag screenshots from different websites in one batch?
Yes. Screenshots can come from different sites, apps, devices, or projects as long as they are supported image files. The tagger applies the same batch tags to every selected input; it does not need to know where a screenshot came from.
For a mixed collection, use a consistent naming system. Short, predictable tags are easier to search and read than long sentences. Examples include:
- 'site-a'
- 'checkout'
- 'mobile'
- 'needs-review'
- 'competitor-research'
- 'design-reference'
If different groups need different labels, process the groups separately. For example, tag checkout screenshots with 'checkout' and 'conversion', then process dashboard screenshots with 'dashboard' and 'navigation'. This avoids applying a broad label to files that do not belong to the same category.
Will Telegram, Instagram, or other apps preserve the tags?
Messaging and social apps often create a new processed copy of an image. They may resize, recompress, crop, or remove metadata. A visible label usually remains visible because it is part of the pixels, although an app can still crop it if the label sits near an edge.
If metadata preservation matters, send the output as a file or document rather than as a normal compressed photo, and use direct transfer whenever possible. If the tag only needs to be seen by another person, mobile-visible mode is safer than relying on a social platform to preserve XMP keywords.
Is a bulk image tagger private?
It can be, but check how the particular service works. Many online image tools upload files to a server for processing. That may be acceptable for public screenshots, but it is a poor default for confidential designs, customer information, internal dashboards, or personal photos.
MediaBrew processes the Bulk Image Tagger in the browser. The selected files are read locally, the metadata or visible PNG is generated on the device, and the original files are not overwritten. No account or server upload is required.
Local processing can be slower for a very large batch because the work uses the phone or computer's available memory and CPU. For a normal group of screenshots, the privacy benefit is usually worth the trade-off.
Does FFmpeg add tags to images?
FFmpeg is primarily an audio and video processing framework. It can read and convert some image formats, and it can be useful when images are part of a video workflow, but it is not the best foundation for format-aware image keyword editing.
Image metadata has container-specific details. JPEG, PNG, and WebP store information differently, and rewriting an image through a video-oriented pipeline may re-encode the pixels or discard fields that were not explicitly preserved. A dedicated image metadata writer is a better fit when the goal is to add XMP keywords without changing the visual image.
For a mobile-visible result, no metadata library can make a gallery display a custom overlay. The dependable solution is to render the label into a new image, which is why the tool offers a separate visible-label mode.
How to choose tags that stay useful
Good tags are short, consistent, and specific enough to distinguish one group from another. Decide whether your tags describe the source, the content, the status, or the intended use, then keep that system consistent.
Avoid creating several versions of the same idea, such as 'to-review', 'needs-review', and 'review-later', unless they genuinely mean different things. Prefer one spelling and one separator. If you need hierarchical information, use separate tags such as 'client-acme', 'project-redesign', and 'status-review' rather than putting an entire sentence in one keyword.
For visible labels, keep the number of tags small enough to read on a phone. Put the most important category first, then add one or two supporting tags. Metadata mode can hold a larger set, but a long keyword list is still harder for people to understand and maintain.
Frequently asked questions
What is the easiest free way to tag multiple photos?
Use a browser-based bulk image tagger. Select the images, enter the tags once, choose metadata or visible labels, and download the processed copies. A local browser tool is especially useful when you do not want to install desktop software or upload the images.
Can I add the same tag to hundreds of images?
Yes, provided the browser and device have enough memory for the batch. For very large archives, process smaller groups and verify the output before continuing. Keeping the original files in a separate folder is recommended.
What image formats are supported?
MediaBrew's Bulk Image Tagger supports JPEG, PNG, and WebP images. It does not process HEIC, AVIF, GIF, or video files in this workflow.
Are image tags visible in every phone gallery?
Embedded metadata tags are not guaranteed to be visible in every gallery. Use mobile-visible labels when the tag must be seen on iPhone and Android without relying on gallery-specific metadata support.
Does the tool overwrite my original photos?
No. The tool creates downloaded output files and leaves the selected originals unchanged. Keep the original folder if you choose mobile-visible mode, because that mode intentionally creates a new labelled PNG.
Start tagging images online for free
For clean cataloguing, choose Embedded metadata. For reliable visibility in mobile galleries and file previews, choose Mobile-visible labels. Both workflows let you add the same tags to a batch without manually opening and editing every screenshot.
Open the free Bulk Image Tagger, add your images, enter your tags, process the batch locally, and test one output in the gallery where you plan to use it. That small verification step helps you choose the right mode before you label an entire archive.