Ic Light
Playground
Try it on WaveSpeedAI!IC-Light V2 is an AI-powered image relighting model. Relight any image with customizable lighting direction. Ready-to-use REST inference API, best performance, no coldstarts, affordable pricing.
Features
IC-Light is an AI-powered image relighting model that transforms the lighting of any photo with a simple text prompt. Change the direction, mood, and quality of light in your images — from dramatic side lighting to soft ambient glow — all without manual editing.
Why Choose This?
-
Text-driven relighting Describe the lighting you want (e.g., “sunlight”, “soft studio light”, “golden hour”) and the model applies it naturally.
-
Directional control Choose from five lighting directions — None, Left, Right, Top, Bottom — for precise control over light placement.
-
Non-destructive transformation Preserves subject details, textures, and colors while only changing the lighting characteristics.
-
Product-ready results Perfect for e-commerce, photography enhancement, and creative projects requiring consistent lighting.
Parameters
| Parameter | Required | Description |
|---|---|---|
| prompt | Yes | Describe the desired lighting effect (e.g., sunlight, studio light, warm glow) |
| image | Yes | Source image to relight (upload or URL) |
| lighting_direction | No | Light direction: None, Left, Right, Top, Bottom |
How to Use
- Upload your image — drag and drop or paste a public URL.
- Write your prompt — describe the lighting style you want (e.g., “sunlight”, “cinematic side lighting”, “soft diffused light”).
- Select lighting direction — choose where the light comes from (Left, Right, Top, Bottom) or None for ambient.
- Run — submit and download your relit image.
Pricing
| Output | Cost |
|---|---|
| Per image | $0.20 |
Best Use Cases
- E-commerce Photography — Standardize product lighting across catalogs without reshooting.
- Portrait Enhancement — Add flattering light to photos taken in poor lighting conditions.
- Creative Projects — Experiment with dramatic lighting for artistic effects.
- Real Estate — Brighten interior shots or add warm, inviting light to property photos.
- Social Media Content — Elevate everyday photos with professional-quality lighting.
Pro Tips
- Use specific lighting terms in your prompt for better results (e.g., “warm golden hour sunlight” vs. just “light”).
- Combine prompt and direction for maximum control — describe the quality while specifying the angle.
- For product shots, “Left” or “Right” directions often create appealing depth and dimension.
- Use “None” direction when you want the prompt to fully control lighting placement.
- Works best with clear subjects and well-defined edges.
Notes
- Ensure uploaded image URLs are publicly accessible.
- For best results, use high-quality source images with clear subjects.
- The model preserves original image resolution.
Authentication
For authentication details, please refer to the Authentication Guide.
API Endpoints
Submit Task & Query Result
set -euo pipefail
export WAVESPEED_API_KEY="your-api-key"
REQUEST_BODY=$(cat <<'JSON'
{
"prompt": "A cinematic ocean wave at sunrise, highly detailed",
"image": "https://interactive-examples.mdn.mozilla.net/media/cc0-images/painted-hand-298-332.jpg",
"lighting_direction": "None"
}
JSON
)
# 1. Submit the prediction.
SUBMIT_RESPONSE=$(curl --silent --show-error --fail-with-body \
-X POST "https://api.wavespeed.ai/api/v3/wavespeed-ai/ic-light" \
-H "Authorization: Bearer ${WAVESPEED_API_KEY}" \
-H "Content-Type: application/json" \
-d "${REQUEST_BODY}")
TASK=$(printf '%s' "${SUBMIT_RESPONSE}" | jq 'if type == "object" and has("data") then .data else . end')
PREDICTION_ID=$(printf '%s' "${TASK}" | jq -r '.id // empty')
if [ -z "${PREDICTION_ID}" ]; then
printf 'Submission response did not contain a prediction id
' >&2
exit 1
fi
RESULT_URL=$(printf '%s' "${TASK}" | jq -r '.urls.get // empty')
if [ -z "${RESULT_URL}" ]; then RESULT_URL="https://api.wavespeed.ai/api/v3/predictions/${PREDICTION_ID}/result"; fi
# 2. Poll until the prediction finishes.
while true; do
RESPONSE=$(curl --silent --show-error --fail-with-body \
"${RESULT_URL}" \
-H "Authorization: Bearer ${WAVESPEED_API_KEY}")
RESULT=$(printf '%s' "${RESPONSE}" | jq 'if type == "object" and has("data") then .data else . end')
STATUS=$(printf '%s' "${RESULT}" | jq -r '.status // empty')
case "${STATUS}" in
completed) printf '%s\n' "${RESULT}" | jq '.outputs'; break ;;
failed|cancelled|timeout) printf '%s\n' "${RESULT}" | jq . >&2; exit 1 ;;
created|processing) sleep 2 ;;
*) printf 'Unexpected status: %s
' "${STATUS}" >&2; exit 1 ;;
esac
doneParameters
Task Submission Parameters
Request Parameters
| Parameter | Type | Required | Default | Range | Description |
|---|---|---|---|---|---|
| prompt | string | Yes | - | Describe the lighting effect you want to apply to the image | |
| image | string | Yes | - | Upload the image you want to relight | |
| lighting_direction | string | No | None | None, Left, Right, Top, Bottom | Choose the direction of the light source |
Response Parameters
| Parameter | Type | Description |
|---|---|---|
| code | integer | HTTP status code (e.g., 200 for success) |
| message | string | Status message (e.g., “success”) |
| data.id | string | Unique identifier for the prediction, Task Id |
| data.model | string | Model ID used for the prediction |
| data.outputs | array | Output values, usually URL strings; some models return text strings or structured result objects (empty when status is not completed) |
| data.urls | object | Object containing related API endpoints |
| data.urls.get | string | URL to retrieve the prediction result |
| data.status | string | Status of the task: created, processing, completed, or failed |
| data.created_at | string | ISO timestamp of when the request was created (e.g., “2023-04-01T12:34:56.789Z”) |
| data.error | string | Error message (empty if no error occurred) |
| data.timings | object | Object containing timing details |
| data.timings.inference | integer | Inference time in milliseconds |
Result Request Parameters
| Parameter | Type | Required | Default | Description |
|---|---|---|---|---|
| id | string | Yes | - | Task ID |
Result Response Parameters
| Parameter | Type | Description |
|---|---|---|
| code | integer | HTTP status code (e.g., 200 for success) |
| message | string | Status message (e.g., “success”) |
| data | object | The prediction data object containing all details |
| data.id | string | Unique identifier for the prediction |
| data.model | string | Model ID used for the prediction |
| data.outputs | array<string | object> | Array of generated outputs (empty when status is not completed). Items are usually URL strings, but may be text strings or structured result objects, depending on the model. |
| data.urls | object | Object containing related API endpoints |
| data.urls.get | string | URL to poll for the prediction result |
| data.status | string | Status: created, processing, completed, or failed |
| data.created_at | string | ISO timestamp of when the request was created |
| data.error | string | Error message (empty if no error occurred) |
| data.timings | object | Object containing timing details |
| data.timings.inference | integer | Inference time in milliseconds |