Media

Batch Image Rename

Batch rename image files using patterns, text replacement, numbering, and case conversion. Returns renamed files as a ZIP download.

file· File resultOpen tool

Quick start

Call this tool from your code in three languages.

cURL

# 1) Upload each file first → returns { filePath }
curl -X POST 'https://api.elysiatools.com/upload/image-batch-rename' \
  -F 'file=@/path/to/imageFiles.ext'

# 2) Call the tool with the returned filePath values
curl -X POST 'https://api.elysiatools.com/en/api/tools/image-batch-rename' \
  -F 'imageFiles=photo1.jpg,photo2.jpg' \
  -F 'renamePattern=Photo_{n:03}' \
  -F 'findText=Text to find in filename' \
  -F 'replaceText=Replacement text' \
  -F 'addPrefix=Text to add at the beginning' \
  -F 'addSuffix=Text to add at the end (before extension)' \
  -F 'startNumber=1' \
  -F 'caseConversion=none'

API reference

Send a POST request with your inputs as JSON. File parameters require a separate upload first.

Endpoint

HTTP

POST https://api.elysiatools.com/en/api/tools/image-batch-rename

Parameters

Name	Type	Required	Description
imageFiles	fileupload required	Yes	—
renamePattern	text	No	Use {name} for original name, {n} for number, {n:03} for padded number, {date}, {time}, {year}, {month}, {day}, {hour}, {minute}, {second}, {ext}
findText	text	No	Leave pattern empty to use this option
replaceText	text	No	—
addPrefix	text	No	e.g., "Vacation_" or "IMG_"
addSuffix	text	No	e.g., "_edited" or "_final"
startNumber	number	No	Starting number for {n} placeholder
caseConversion	select	No	—

File-type parameters must be uploaded first via POST /upload/image-batch-rename, then the returned filePath is passed to the corresponding file field.

Response format

File result

JSON

{
  "filePath": "/public/processing/randomid.ext",
  "fileName": "output.ext",
  "contentType": "application/octet-stream",
  "size": 1024,
  "metadata": {
    "key": "value"
  },
  "error": "Error message (optional)",
  "message": "Notification message (optional)"
}

MCP integration

Add this tool to your Model Context Protocol server so AI agents can list and call it.

Server configuration

Add this block to your MCP client configuration:

mcp.json

{
  "mcpServers": {
    "elysiatools-image-batch-rename": {
      "name": "image-batch-rename",
      "description": "Batch rename image files using patterns, text replacement, numbering, and case conversion. Returns renamed files as a ZIP download.",
      "baseUrl": "https://api.elysiatools.com/mcp/sse?toolId=image-batch-rename",
      "command": "",
      "args": [],
      "env": {},
      "isActive": true,
      "type": "sse"
    }
  }
}

List available tools

After connecting to the SSE endpoint, list the exposed tools:

tools/list

{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/list"
}

Call this tool

Invoke the tool by its id, passing arguments built from its parameters:

tools/call

{
  "jsonrpc": "2.0",
  "id": 2,
  "method": "tools/call",
  "params": {
    "name": "image-batch-rename",
    "arguments": {
  "imageFiles": [
    "photo1.jpg",
    "photo2.jpg"
  ],
  "renamePattern": "Photo_{n:03}",
  "findText": "Text to find in filename",
  "replaceText": "Replacement text",
  "addPrefix": "Text to add at the beginning",
  "addSuffix": "Text to add at the end (before extension)",
  "startNumber": 1,
  "caseConversion": "none"
}
  }
}

Chain multiple tools in one session with a comma-separated toolId list, e.g. /mcp/sse?toolId=png-to-webp,jpg-to-webp,gif-to-webp (max 20).

File parameters accept a public file URL only (https://…). Local paths, data: URIs, and Base64 strings are not supported.

Questions or issues? Contact [email protected]