[Feature] Add Support for Date Range Variables in Storage Templates

[danielcebrian]

I have searched the existing feature requests, both open and closed, to make sure this is not a duplicate request.

• Yes

The feature

Description

I would like to request a new variable for storage templates that allows creating a single folder for an album with a date range from the oldest to the newest photo, instead of creating separate folders for each day.

Current Behavior

Currently, when using templates like:

{{y}}/{{#if album}}{{album}} ({{dd}}-{{MM}}-{{yy}}){{else}}Others/{{MM}}{{/if}}/{{filename}}

This creates multiple folders for the same album with different dates:

• "Trip to New York (01-02-22)"
• "Trip to New York (02-02-22)"
• "Trip to New York (03-02-22)"

Each day of the trip gets its own folder, which clutters the storage structure.

Requested Feature

I would like a new variable or function that creates a date range, something like:

{{y}}/{{#if album}}{{album}} ({{dateRange start="oldest" end="newest" format="dd-MM-yy"}}){{else}}Others/{{MM}}{{/if}}/{{filename}}

Which would generate a single folder like:

• "Trip to New York (01-02-22 to 07-03-22)"
• "Trip to Morocco (01-02 to 07-02-22)"

Use Case

This would be particularly useful for trips, events, and other albums that span multiple days, allowing for a cleaner folder structure that keeps all related photos together while still providing date context.

Available Variables

According to the documentation, Immich currently supports the following date variables:

• {{y}}, {{yy}} - Year
• {{M}}, {{MM}}, {{MMM}}, {{MMMM}} - Month
• {{W}}, {{WW}} - Week
• {{d}}, {{dd}} - Day
• {{h}}, {{hh}} - Hour
• {{m}}, {{mm}} - Minute
• {{s}}, {{ss}}, {{sss}} - Second

But there's no built-in way to create a date range from the album's photos.

Thank you for considering this feature request!

Platform

• Server
• Web
• Mobile

[danielcebrian]

I don't know if this solution would work in the file "immich-template-modification.ts". I have uplodad the IA solution for this case (immich-template-modification.zip), but I don't know how to prove it. Plase, same help here. The specific code:

// New method to get album date range
private async getAlbumDateRange(ownerId: string, albumId?: string): Promise<string | null> {
if (!albumId) return null;

try {
  // Get all assets in the album
  const assets = await this.assetRepository.getAssetsByAlbumId(ownerId, albumId);
  
  if (!assets || assets.length === 0) return null;
  
  // Find oldest and newest dates
  let oldestDate: Date | null = null;
  let newestDate: Date | null = null;
  
  for (const asset of assets) {
    const fileDate = asset.fileCreatedAt;
    if (!fileDate) continue;
    
    if (!oldestDate || fileDate < oldestDate) {
      oldestDate = fileDate;
    }
    
    if (!newestDate || fileDate > newestDate) {
      newestDate = fileDate;
    }
  }
  
  if (!oldestDate || !newestDate) return null;
  
  // Format the date range
  const systemTimeZone = Intl.DateTimeFormat().resolvedOptions().timeZone;
  const oldestDt = DateTime.fromJSDate(oldestDate, { zone: systemTimeZone });
  const newestDt = DateTime.fromJSDate(newestDate, { zone: systemTimeZone });
  
  // Check if dates are in the same year
  if (oldestDt.year === newestDt.year) {
    // Same year
    if (oldestDt.month === newestDt.month) {
      // Same month and year
      if (oldestDt.day === newestDt.day) {
        // Same day - just use one date
        return oldestDt.toFormat('dd-MM-yy');
      } else {
        // Same month, different days
        return `${oldestDt.toFormat('dd')} to ${newestDt.toFormat('dd-MM-yy')}`;
      }
    } else {
      // Different months, same year
      return `${oldestDt.toFormat('dd-MM')} to ${newestDt.toFormat('dd-MM-yy')}`;
    }
  } else {
    // Different years
    return `${oldestDt.toFormat('dd-MM-yy')} to ${newestDt.toFormat('dd-MM-yy')}`;
  }
} catch (error) {
  this.logger.error(`Error calculating album date range: ${error}`);
  return null;
}

}

[exciton]

Albums already have start and end date fields, which seem to be populated automatically.

To solve this problem those fields can be added to the storage template as e.g. album-start-year, album-end-month, etc. Then any combination of folder naming is available.

[exciton]

Created a PR to generically implement this: #17188

[danielcebrian]

Thank you Exciton for your help!