Local File System Batch Image Reader - n8n Workflow

Learn how to use this essential n8n workflow to read multiple binary files (like JPGs) from a local disk directory using wildcards. Essential core logic n8n templates.

Workflow Preview

Ready to automate?

Download this n8n workflow template and start using it instantly.

Who is this best for?


  • Users who operate a self-hosted n8n instance using Docker or similar containerization.

  • Developers needing to process batches of local files (images, logs, documents).

  • Automation specialists looking for simple, robust n8n templates for file handling.

  • Anyone needing to understand how the core 'Read Binary Files' n8n node functions.

Overview

Handling local files is a critical requirement for many self-hosted n8n deployments. This simple yet powerful n8n workflow demonstrates the core ability to read multiple files simultaneously using a path selector that includes a wildcard (*). This is especially useful for pipelines that require ingesting a large volume of data—such as images, log files, or configuration backups—before passing them to subsequent processing n8n nodes. By using the specialized Read Binary Files n8n node, the automation ensures efficient retrieval of all matching files (in this case, all .jpg files within the /data/lol/ directory) and makes the binary data readily available for the rest of your n8n workflow.

How it Works

This automation follows a straightforward, two-step linear process, activated manually to facilitate testing and deployment preparation:


  1. Start Execution: The n8n workflow begins when the user manually clicks the 'Execute Workflow' button, utilizing the On clicking 'execute' n8n trigger.

  2. Batch File Loading: The execution proceeds to the Read Binary Files n8n node. This crucial n8n node is configured to look for files matching the pattern /data/lol/*.jpg. The n8n node searches the specified local path (which must be accessible by the n8n container or process) and collects all files matching the .jpg extension. Each file is then output as a separate item, retaining its binary data and filename, ready for further steps in the n8n workflow.

Installation Guide


  1. Import the n8n Workflow: Copy the provided JSON data and navigate to your n8n instance. Go to 'Workflows', click 'New', and select 'Import from JSON' to load this n8n template.

  2. Ensure File Access: If running n8n in Docker, ensure that the path /data/lol/ exists on the host machine and is mounted as a volume accessible by the n8n container.

  3. Populate the Directory: Place some test JPG files inside the designated directory (/data/lol/).

  4. Configuration Check: Open the Read Binary Files n8n node and verify that the File Selector parameter (/data/lol/*.jpg) matches your desired path and file type. Adjust the path if necessary for your server environment.

  5. Test: Use the manual 'Execute Workflow' n8n trigger to run the flow and confirm that the n8n node successfully reads the binary files.

Node Details

On clicking 'execute' (Manual Trigger)

Function: Serves as the starting n8n trigger for immediate manual testing. It initiates the n8n workflow execution without requiring a scheduled interval or external webhook.
Key Configuration: Standard manual n8n trigger, requiring no specific credentials or parameters.

Read Binary Files

Function: This powerful n8n node handles low-level file system operations, specifically reading the content of binary files. In this n8n workflow, it is used to batch load all relevant images.
Key Configuration:
File Selector: /data/lol/.jpg (This uses a wildcard (*) to tell the n8n node to select all files ending in .jpg within the /data/lol/ directory. This configuration is essential for batch processing in this n8n workflow.)

Related n8n Workflows

Free

Nodes: 2 Nodes
Updated: December 26 2025
View all
Created by
amudhan
amudhan

Featured*