AI Photo Renamer with Custom Directives: Brand-Aware, Ecommerce, Pinterest Style (2026)
Most AI photo renamers generate the same generic descriptive names for everyone. Here is how custom directives let you bias the AI toward your naming style — brand-first, ecommerce, Pinterest, niche keywords.
Table of Contents
The hidden problem with vanilla AI photo renamers
Most AI photo renamers — including the standard SammaPix tool until April 2026 — work the same way: they look at the image, run it through a multimodal model like Google Gemini, and generate a neutral, SEO-friendly descriptive filename. That is fine for a blog post or a travel album. It is a quiet failure for everyone else.
A few real examples from a support email we received this week. The customer had 200 product photos for an ecommerce store and used the standard AI rename:
- Got:
woman-wearing-apron-bookshelves.jpg— accurate but useless for a Shopify product page - Wanted:
vargen-beige-canvas-apron-001.jpg— brand, color, material, SKU number
The customer's exact words: “Is there any way to give a directive on what title to create for the AI renamer tool? If not, please let me know, as I would like to try a different alternative and close my account.” Fair complaint — the underlying AI model is fully capable of producing the brand-first version. It just had no way to know that is what the user wanted.
The fix is straightforward: add an optional field where the user types a one-line preference, and inject that text into the model prompt as a soft user directive. We shipped exactly that two days after the email. This article walks through what it looks like in practice, what works, and where the AI silently ignores you.
What is a custom AI directive?
A custom AI directive is a single sentence (max 200 characters) that you append to the AI rename prompt. It tells the model how you want the filename to look, in addition to what is in the image. The directive is the same for every photo in the batch — you write it once and it is applied to all of them.
On the server side, the prompt the AI receives looks roughly like this (simplified):
You are an SEO expert. Analyze this image and generate an SEO-optimized filename and alt text. [USER DIRECTIVE - apply unless it conflicts with the rules below] Always include the brand name if visible. Focus on color and material for ecommerce listings. [END USER DIRECTIVE] Rules for filename: - Lowercase, hyphenated, 3-6 words ideal - Describe exactly what you see - No "image", "photo", "picture" ...
The directive sits in its own labeled block above the technical rules. The model treats it as a user preference. When your preference clashes with a technical rule (for example you ask for UPPERCASE filenames or spaces), the technical rule wins. That is intentional — it keeps filenames portable and prevents prompt injection from breaking the output schema.
Why 200 characters and not 2000?
Two reasons. First, every additional token in the prompt is a token billed to the API. Across thousands of users this compounds. Second and more importantly, vague directives produce inconsistent results. A 200-character cap forces clarity — you have to pick the one or two preferences that matter most. In our testing, three ten-word directives outperformed a single hundred-word essay nine times out of ten.
5 directive recipes that actually work
We tested over fifty directive variations on a fixed set of 30 mixed photos (products, portraits, landscapes, food, screenshots). Here are the five recipes that produced consistent, useful results.
1. Brand-first (ecommerce / DTC)
Directive: Always include the brand name if visible in logos or labels. Format: brand-product-color-material.
When the AI sees a logo, watermark, or brand text in the image, it extracts the brand and prefixes it. Best for product catalogs, marketplace listings, and DTC sites where the brand is a primary search keyword. Falls back gracefully when no brand is visible.
2. Ecommerce attribute-rich
Directive: Ecommerce style: focus on color, material, and product category. Skip background details.
Best for product photography where Shopify, WooCommerce, and Etsy surface filenames in image search. The AI prioritizes attributes shoppers actually filter on (color, material, type) and drops studio/setup details that add no SEO value.
3. Pinterest aesthetic
Directive: Pinterest aesthetic naming, max 4 words, focus on mood and style words.
Pinterest's Smart Image Search responds well to short aesthetic descriptors. This directive trades specificity for mood-richness — it produces names like cozy-autumn-coffee-flatlay instead of brown-coffee-cup-saucer-leaves. Useful for lifestyle bloggers, mood boards, and visual content.
4. Niche keyword anchor
Directive: Always include the keyword "organic skincare" somewhere in the filename.
A risky one — keyword stuffing into image filenames is rarely a good idea on its own. But for niche affiliate or single-topic sites, anchoring every image to the page's primary keyword can lift impressions in Google Image Search. Use sparingly and only when the keyword is genuinely descriptive.
5. Travel + location
Directive: Travel photo style: include location landmarks if recognizable. Otherwise focus on activity and scenery.
Vision models recognize many famous landmarks (Colosseum, Eiffel Tower, Sigiriya, Taj Mahal) and will work them into the filename. Pair this with the Batch Rename tool and the {exif:date} token for chronological ordering across the trip.
Here is what a real before/after looks like across these directives, starting from the same product photo:
| Directive | Generated filename |
|---|---|
| No directive (vanilla) | woman-wearing-apron-bookshelves.jpg |
| Brand-first | vargen-beige-canvas-apron-portrait.jpg |
| Ecommerce attribute-rich | beige-canvas-apron-cooking-uniform.jpg |
| Pinterest aesthetic | warm-kitchen-portrait-aesthetic.jpg |
| Niche keyword anchor | handmade-apron-organic-skincare-shoot.jpg |
| Travel + location | artisan-workshop-tuscany-cooking-class.jpg |
Same image. Six different filenames. The directive is the only variable that changed.
Tutorial: how to use the Custom Directive field on SammaPix
Three steps. End to end takes under two minutes after the first time you write your directive.
Step 1 — Open the AI Renamer and add files
Visit sammapix.com/tools/ai-rename. Drag your photos onto the dropzone or click to browse. The tool accepts JPG, PNG, WebP, GIF, and AVIF. Once you have files in the batch, additional controls appear under the file list.
Step 2 — Open the Custom AI directive bar
Below the language selector you will see a dashed bar labeled Custom AI directive. If you are on the free plan you see a lock icon and a Pro badge — clicking it opens the upgrade dialog. If you are on Pro, clicking opens a textarea where you can type your directive.
The textarea has a live character counter (200 max), four quick-fill examples you can click to populate, and a Clear button. The placeholder rotates between four example directives every four seconds when the field is empty — useful when you want inspiration but do not want to type from scratch.
Step 3 — Run Rename All and review
Click Rename All. Each file is sent to Google Gemini together with your directive. The AI processes them in parallel and the new filename appears next to each row as soon as the response arrives. You can edit any individual filename inline if you want to override the AI for that specific photo.
When you are happy with the results, download the renamed files individually or as a ZIP archive. The directive persists across batches in the same session — refresh the page to clear it.
Custom directive vs pattern tokens — when to use which
A custom directive is not always the right tool. Sometimes you want deterministic renaming — every file follows the exact same pattern, numbered sequentially, with no AI involvement. For that, the free Batch Rename tool is a better fit. It supports 13 pattern tokens including {exif:date}, {exif:camera}, {n:3}, find & replace with regex, and case conversion. No AI calls, no rate limits, unlimited files.
Use the table below to pick the right approach for your batch:
| When | Tool to pick | Why |
|---|---|---|
| You already know the exact naming scheme | Batch Rename (free) | Pattern tokens are deterministic and zero cost |
| Photos are content you have not seen yet (downloaded album, client deliverable) | AI Renamer + directive | Only the AI can describe what is in each photo |
| Chronological photo archive ordered by date taken | Batch Rename with {exif:date}-{n:3} | Only EXIF date gives you a reliable chronology |
| Ecommerce product batch where brand and material vary per photo | AI Renamer with brand-first directive | A pattern token cannot extract brand from an image |
| Strip a common prefix from 500 files (IMG_ → vacation-) | Batch Rename / Find & Replace | String replace runs in milliseconds — no AI cost |
| Mixed batch where you want descriptive names for new photos but consistent IDs for products | Both — sequential pipeline | AI Rename first, then Batch Rename to add SKU prefix |
Most professional workflows we have seen use both tools in sequence. AI Renamer first (with directive) for descriptive content, then Batch Rename to add a numeric prefix or fold in EXIF date. The two tools are designed to chain.
Limits, gotchas, and what the AI ignores
Custom directives are powerful but not magic. Five things worth knowing before you commit a 500-photo batch:
The AI silently overrides UPPERCASE, spaces, and special characters
If your directive asks for UPPERCASE FILENAMES or spaces between words, the AI will silently fall back to the technical rules (lowercase, hyphenated). This is by design — filenames must be portable across Windows, macOS, Linux, and CDNs. No warning is shown; you just get properly-formatted names.
Brand recognition is imperfect
The AI is great at reading clearly visible brand text but it can hallucinate brand names from ambiguous logos. In our test set, brand recognition accuracy was around 85% on photos with clearly visible logos and dropped to about 60% when the brand text was rotated, partially occluded, or stylized. Always review the first batch before committing to a directive.
The directive does not affect alt text generation strategy
Currently the directive is applied to filename generation only. The accompanying alt text follows the standard accessibility template. If you need to influence alt text style as well, drop us a note — that is on the roadmap.
The directive cannot reference other files in the batch
Each photo is processed independently. You cannot write a directive like “number these consecutively starting from 042” — that is a Batch Rename pattern job. Use {n:3} in Batch Rename for sequential numbering after AI Rename has done its descriptive pass.
Prompt injection attempts are stripped
The directive is sanitized server-side: newlines and control characters are removed before it reaches the model. Attempts to escape the directive block (writing things like [END USER DIRECTIVE] inside the field) collapse to plain text. The model still treats the directive as a soft user preference, never as a system instruction.
Once you understand these limits, the directive becomes a quiet force multiplier. A blogger we work with renamed 480 photos for a new niche site in 12 minutes — every filename anchored to the site's primary keyword without any manual editing. The same job manually would have taken a full afternoon.
Want to combine AI rename with image compression and WebP conversion in a single pipeline? See the AI image renaming SEO guide for the full optimization workflow, or the batch rename photos with AI tutorial for the original vanilla approach.
FAQ
- What is a custom AI directive when renaming photos?
- A custom AI directive is a freeform instruction (up to 200 characters) you give to the AI photo renamer to bias the generated filenames toward a specific style — for example brand-first, ecommerce, Pinterest aesthetic, or with a niche keyword always present. The same image can produce very different filenames depending on the directive you provide.
- Why do I need a custom directive if the AI is already generating SEO-friendly names?
- A vanilla AI renamer treats every user the same: it produces a neutral, descriptive name based on what it sees. That works for blogs and travel photos, but it fails when you have a domain-specific naming convention. An ecommerce store might want color and material first; a Pinterest-focused brand might want short aesthetic names; a niche affiliate site might want a specific keyword in every filename. The directive bridges that gap.
- Is the Custom AI directive feature free on SammaPix?
- The Custom AI directive field on SammaPix is a Pro-only feature ($9/month or $79/year). Free users can still use the AI Renamer with the standard prompt — and they can use the free Batch Rename tool, which provides mechanical pattern-based renaming with 13 tokens including EXIF date taken, camera model, and ISO.
- Can I write multi-line directives or use markdown?
- No. The directive field strips newlines and control characters before sending to the model — this is a defense against prompt-injection attacks. You should write a single sentence or two, comma-separated. The 200-character cap forces clarity: a short, specific directive almost always outperforms a long, vague one.
- Will the AI ignore my directive if it contradicts the technical rules?
- Yes. The directive is injected as a soft user preference in a separate block of the prompt. The technical rules (lowercase, hyphenated, 3-8 words, no special characters) take priority. If your directive conflicts — for example you ask for spaces in filenames — the AI will silently fall back to the technical rule. This keeps generated filenames safe across all operating systems.
- How does this compare to the free Batch Rename tool?
- Batch Rename is mechanical: you write a pattern with tokens (like {exif:date}-{name}-{n:3}) and the tool fills it in deterministically. AI Renamer with directive is descriptive: the AI looks at each image and generates a filename that respects your stylistic preference. Use Batch Rename when you already know the naming scheme. Use AI Renamer with directive when you want descriptive names but with a specific bias — for example always extracting the brand from a product photo.
