Photography Articles

How to Use Search Function in SendPhoto: A Pro Guide

Master SendPhoto's search. Our guide shows you how to use search function with advanced filters & tips to find any photo fast. Perfect for busy photographers.

Published July 10, 2026

A client has just messaged, asking for “that golden hour shot near the trees” or “the photo where the bride is laughing during prep.” The gallery is already delivered, the shoot had hundreds or thousands of files, and manual scrolling is the slowest possible way to answer a simple request. That's usually the moment photographers start caring about search.

The useful version of search isn't just typing a word and hoping for the best. It's knowing how to search by filename, folder, and metadata in a way that matches how photographers work. That means terms like bride_prep, golden_hour, family_formals, RAW, or a client surname matter more than generic search examples ever do.

Table of Contents

Find Any Photo Instantly with Basic Search

The fastest way to learn how to use search function tools in a gallery is to stop treating search like a last resort. It should be the first move any time someone asks for one image, one moment, or one subset of a shoot.

A gallery search bar is built for this exact job. Instead of scrolling through folders or timelines, type the most likely word tied to the photo. That might be a filename fragment, a folder label, a tag, or a scene description such as ceremony, bride_prep, sparklers, or golden_hour.

Screenshot from https://sendphoto.io

Start with the obvious term first

Basic search works best when the term is specific enough to narrow the gallery without overcomplicating the query.

A practical sequence looks like this:

  1. Use one strong keyword first. Start with bride, prep, reception, cake, or the client name.
  2. Watch the preview update. Search interfaces that use real-time previews and auto-completion can reduce average query formulation time by up to 40%, and the search field should show at least 27 characters so longer queries stay visible, as noted in Jahia's guidance on internal search UX.
  3. Refine only if needed. If ceremony returns too much, try wedding_ceremony or a folder name tied to the timeline.
  4. Stick to your own naming habits. Search can only surface words that exist somewhere in the file, folder, or metadata.

Practical rule: Search the way the gallery was labeled, not the way the memory is described.

What basic search is good at

Basic search is ideal for quick retrieval when the gallery already has decent structure. It replaces scrolling in a few common situations:

  • Filename recall: If export names contain a couple's surname or event code, searching that fragment pulls matching files quickly.
  • Folder recall: Terms like getting_ready, ceremony, or portraits work when folders mirror the day's flow.
  • Tag recall: Search becomes much more useful once common labels are applied consistently across the shoot.

SendPhoto includes search across the gallery, which makes it possible to look up photos by entered terms instead of digging through a full delivery manually. For day-to-day client support, that's often enough to answer most “can you resend that one image?” messages without breaking rhythm.

Go Deeper with Advanced Search Filters and Operators

Advanced search earns its keep the first time a client asks for “the bride prep shots at golden hour, but not the blurry test frames” and you need the answer in seconds, not after five minutes of clicking around a full gallery. One-word search terms stop being useful once a wedding, commercial shoot, or multi-day event gets large enough to stack similar moments on top of each other.

An infographic titled Advanced Search Filters explaining five steps to refine photo searches using keywords and operators.

The practical shift is simple. Stop searching with single nouns, and start searching with conditions.

For photographers, those conditions usually come from metadata and gallery structure. The useful fields are not abstract. They are the labels already tied to how a shoot was edited and delivered: tag:bride_prep, folder:getting_ready, date:2024-06-15, rating:5, or an exclusion like NOT folder:culls. If your tagging is inconsistent, advanced search will feel unreliable. A clear metadata management workflow for photo libraries fixes that upstream.

Use operators to narrow, widen, or exclude

Operators help combine the terms you already use in real jobs:

  • AND returns files that match multiple conditions
  • OR returns files that match either valid term
  • NOT removes files tied to a term, tag, or folder you do not want

Filters add precision on top of that. Instead of searching the entire gallery for golden_hour, you can limit the search to a single folder, date, or rating set. That matters in photographer workflows because the same phrase can appear across prep, portraits, selects, exports, and culls.

After the setup, a short product demo can make the query logic easier to visualize.

Search operators and filters cheat sheet

Operator/Filter Example What It Does
AND bride AND golden_hour Returns files that contain both terms
OR ceremony OR vows Returns files that match either term
NOT portraits NOT culls Excludes files tied to unwanted terms
tag: tag:favorite Limits results to a tag
folder: folder:getting_ready Searches within one folder or collection
date: date:2024-06-15 Pulls files from a specific date
Combined query tag:5-star AND date:2024-06-15 NOT folder:culls Finds highly rated files on one date while excluding culls

Queries that save time in real galleries

The value here is speed under pressure. A couple wants every usable image from bride prep. A brand client wants only approved product angles for one SKU. An associate shooter needs all golden hour portraits from a specific date without seeing rejects.

A few patterns come up constantly:

  • tag:bride_prep AND golden_hour
  • folder:ceremony AND vows NOT culls
  • product_sku_123 AND tag:approved_selects
  • family_formals AND rating:5
  • date:2024-06-15 AND sunset_portraits NOT duplicates

The trade-off is maintenance. Advanced syntax only works when naming stays steady across imports, culling, and delivery. If one gallery uses bride_prep, another uses bridal_prep, and a third uses getting_ready_bride, search results fragment fast. The fix is not more searching. The fix is choosing one format and sticking to it.

Search gets faster when the query matches the way the shoot was tagged, culled, and handed off.

Photographer-Specific Search Scenarios

Generic search advice usually stops at “type a keyword.” That misses how photographers label work. Real galleries live on terms like bride_prep, wedding_ceremony, family_formals, flatlays, product_sku_123, and approved_selects.

A professional photographer sits by a lake editing landscape photos on his laptop next to his camera gear.

Many tutorials miss that gap. 68% of wedding photographers report clients struggle to find specific photos like wedding_ceremony or bride_dress because of unclear search syntax, according to the supporting reference cited in this photographer-specific search syntax discussion.

Wedding galleries

A couple asks for “all the bride prep photos with the champagne robe.” Searching bride alone will usually return too much. A tighter query combines timeline and tag language, such as folder:getting_ready AND tag:bride_prep.

That's also where underscore-based tags help. Terms like bride_prep or first_look stay cleaner than loose phrases because they keep the same structure across every gallery.

bride prep, bridal prep, and getting ready bride sound similar to a person. Search treats them as different inputs unless metadata is consistent.

Commercial and product work

Commercial jobs tend to break when labels are too casual. A team may need every vertical crop of a single product line, or only the final approved selects for one SKU.

A practical search might look like product_sku_123 AND tag:vertical AND tag:approved. That kind of syntax matters more than broad folder browsing because commercial archives often contain multiple versions of nearly identical shots.

Portrait and family sessions

Portrait workflows are usually more personal and less technical, but the same search discipline helps. A family may ask for “every favorite with grandma” months after delivery.

If the gallery uses tags such as grandma, favorites, or extended_family, that request becomes manageable. If not, the search bar can only work with filenames and folder names, which is rarely enough for relationship-based recall.

The common thread across all three specialties is simple. Search improves when metadata reflects how clients ask for images, not just how the photographer imported them.

How to Organize Galleries for Powerful Searching

A client emails six months after delivery and asks for “the bride prep photos with window light” or “those golden hour portraits before sunset.” Search only works that fast if the gallery was built for those requests from the start.

A five-step infographic guide on how to organize digital photos for a more powerful search experience.

Build a search-friendly naming system

The folder structure should mirror how a photographer will retrieve work later, not just how the cards were imported on shoot day. For weddings, that usually means timeline-based folders such as bride_prep, ceremony, family_formals, golden_hour_portraits, and reception. For commercial work, it may be sku_123, approved_selects, or spring_campaign.

Three parts need to stay consistent:

  • Folder names: Use repeatable stage or deliverable names across every job.
  • Tags: Keep one approved version of each concept, such as first_look instead of mixing firstlook, first look, and reveal.
  • File labels or metadata fields: Add location, people, usage status, or lighting notes while the shoot is still fresh.

That consistency pays off later. A search for folder:golden_hour_portraits AND tag:approved is only useful if those labels exist in the same form every time.

Studios that want a broader framework for asset planning can borrow ideas from this guide to managing real estate digital assets, because the same failure shows up in both fields. Naming drift makes retrieval slower, especially once the archive spans years.

Use tags that match real search behavior

Photographers often tag from memory. Clients search from description. Those are not always the same thing.

I've found it helps to treat tags as a translation layer between studio shorthand and client language. If the internal tag is bride_prep, add supporting terms elsewhere in your system so “bridal prep,” “getting ready,” and “bride getting ready” still point to the same set of images. The same applies to terms like golden_hour, sunset_portraits, and evening_light. Search gets messy when each gallery uses a different phrase for the same visual moment.

A few habits keep that under control:

  • Create a tag list before busy season. Decide on terms once, then reuse them.
  • Use one separator style. Underscores keep multi-word tags readable and consistent.
  • Prioritize high-retrieval categories. Start with moments clients request most often, such as bride_prep, first_look, family_formals, details, and dance_floor.
  • Clean up legacy galleries selectively. Retag the jobs you revisit most, rather than trying to fix the whole archive at once.

For a more detailed setup process, this photo organization workflow for galleries and archives pairs well with a search-first system.

Troubleshooting Common Search Issues

The most common search problem isn't a broken tool. It's a mismatch between the query and the way the gallery was organized.

Why no results happens

“No results” usually comes from one of a few causes. The term may be misspelled, the wrong operator may be used, or the photo may never have received the tag the search depends on.

Sometimes the issue is structural. If files were uploaded in bulk without a consistent folder plan, the gallery may still work visually but fail when someone searches by logic instead of memory. A simple reference like these best practices for digital folder structure can help identify where naming drift started.

A fast recovery checklist

When search comes up empty, run this list in order:

  1. Check spelling first. One missing character can block the intended match.
  2. Shorten the query. Search bride before bride_golden_hour_laughing.
  3. Remove one filter at a time. Over-filtering is a common cause of empty results.
  4. Confirm the metadata exists. If the photo was never tagged, search can't invent the label.
  5. Review the upload stage. A disorganized import often creates search problems later, so a cleaner bulk file upload workflow can prevent that issue upstream.

When search fails, the fix is usually in the naming or tagging, not in the box itself.

Conclusion Your Workflow Superpower

Knowing how to use search function tools well changes gallery delivery in a very practical way. It cuts out scrolling, shortens response time, and makes old work easier to retrieve when clients come back with specific requests.

The difference shows up in small moments. A wedding client asks for one prep image. A commercial team needs one SKU variation. A family wants every favorite with one relative. Search handles those requests cleanly when filenames, folders, and tags follow a consistent system.

That's a significant advantage. Search isn't just a convenience feature. It becomes part of the delivery workflow, right alongside culling, exporting, and sharing.


SendPhoto gives photographers a practical way to deliver searchable client galleries with folders, tags, batch edits, and client-ready sharing in one place. For studios that want faster handoffs and less back-and-forth when someone asks for a specific image later, SendPhoto is worth a look.

Need a cleaner way to deliver the finished gallery?

SendPhoto gives photographers client galleries with passwords, watermarks, collections, and download controls.