- actions_required
- file:view
- file:create
- file:update
- entity:view
- entity:update
- description
- Converts various image formats (PNG, WebP, TIFF, AVIF, GIF) to JPEG with batch support
- endpoint
- https://image-to-jpeg.arke.institute
- endpoint_verified_at
- 2026-01-21T04:14:30.931Z
- input_schema
- properties
- entity_id
- description
- Source image file entity to convert (supports PNG, WebP, TIFF, AVIF, GIF)
- type
- string
- entity_ids
- description
- Array of image file entity IDs to convert (supports PNG, WebP, TIFF, AVIF, GIF)
- type
- array
- options
- description
- Conversion options
- properties
- batch_size
- description
- Entities per Lambda call (default: 10)
- type
- number
- lambda_concurrency
- description
- Max parallel Lambda calls (default: 10)
- type
- number
- quality
- description
- JPEG quality 1-100 (default: 85)
- type
- number
- type
- object
- type
- object
- output_description
- For each input image entity, the service creates a new JPEG file entity and uploads the converted image content to it. The new JPEG entity is placed in the same collection as the source image (inheriting the source's collection relationship, or using an explicitly provided collection ID). The JPEG filename is derived from the source filename with the extension replaced by .jpg (e.g. 'photo.png' becomes 'photo.jpg'). The source entity is not modified or deleted — it remains as-is. If the source image is already in JPEG format, no conversion is performed and no new entity is created; the original entity ID is returned unchanged. For GIF images, only the first frame is extracted and converted. JPEG quality defaults to 85 but can be configured via options.
- output_relationships
- Each new JPEG entity has a 'derived_from' relationship pointing to its source image entity
- Each source image entity receives a 'has_derivative' relationship pointing to the new JPEG entity
- These two relationships are created as a single bidirectional pair (source_predicate: 'derived_from', target_predicate: 'has_derivative')
- No relationships are created for source images that are already JPEG — they are skipped entirely
- output_tree_example
- Input:
file 'scan.png' (entity II..abc, collection II..col1)
After conversion:
file 'scan.png' (entity II..abc, unchanged)
└── has_derivative → file 'scan.jpg' (entity II..xyz, new, in collection II..col1)
file 'scan.jpg' (entity II..xyz)
└── derived_from → file 'scan.png' (entity II..abc)
If source is already JPEG:
file 'photo.jpg' (entity II..def) → skipped, no new entity created
- status
- active