# Support

> Get help through built-in chat, a founder meeting, Discord, or email and include a safe, complete diagnostic packet.

- Canonical HTML: https://superlumin.al/docs/support
- Markdown endpoint: https://superlumin.al/docs/support.md
- Structured page data: https://superlumin.al/docs/support.json
- Last updated: 2026-08-04
- Author: Superluminal Engineering

## Related Superluminal Research

- [The Superluminal render interface](https://superlumin.al/interface): A visual tour of Superluminal's Blender add-on, file checks, live job page, previews, and output downloads.
- [Blender project dependencies](https://superlumin.al/dependencies): Before upload, Superluminal checks textures, linked Blender files, UDIMs, sequences, caches, fonts, and other external inputs.
- [Blender render engine compatibility](https://superlumin.al/compatibility/render-engines): Superluminal renders Cycles and EEVEE image sequences with Blender 4.0 through 5.2. Choose the farm version and output format before submission.

## Complete documentation

You can reach us four ways. Whichever you choose, include the diagnostic details below in your first message. That saves a round trip.

- [Built-in support chat](/support): Open Support from the taskbar for help in the context of the signed-in app.
- [Meet us](https://cal.com/superluminal/founders): Book a 30-minute Google Meet for a project, render-pipeline question, or issue that is easier to discuss live.
- [Discord community](https://discord.gg/rUJPnMycqx): Ask the team and community for quick, non-private help.
- [Email](mailto:hello@su.lu): Use hello@su.lu for private account, billing, or production questions.

## Before contacting support

For a render issue, collect:

- organization and project name
- Job ID and the exact affected frame or range
- Blender major/minor and Superluminal add-on version
- timestamp with timezone
- upload mode, render pattern, image format, and relevant experimental toggles
- a downloaded log or the worker's final error, with secrets redacted
- short reproduction steps
- expected result and actual result

For a visual mismatch, include the full downloaded frame and a local comparison when you are allowed to share the scene content. A compressed web-preview screenshot is useful context but not proof of the original image data.

### Never send secrets

Do not send passwords, access tokens, API keys, session files, signed upload/download URLs, payment details, or credential-bearing request headers. Redact them from logs and screenshots.

## Fast self-checks

### Reproduce one frame

Use the exact failed frame locally and remotely with matching settings.

### Check current state

Confirm organization balance, project, job status, frame state, and the selected Blender and add-on versions.

### Inspect logs

Select the frame in the job page, search the log, apply severity filters, and download it.

### Separate packaging from rendering

If you suspect PROJECT path mapping, submit one representative frame as a ZIP job.

### Preserve evidence

Record IDs and timestamps before deleting or duplicating anything.

## Where to look first

- [Add-on troubleshooting](/docs/blender-addon/troubleshooting): Connection, projects, submission, paths, frames, and downloads.
- [Job details](/docs/web-ui/job-details): Use the frame workspace, operation chart, machine telemetry, and logs.
- [Billing](/docs/web-ui/billing): Resolve blocked funds, capacity, checkout, or referral questions.
- [Availability](/docs/availability): Check whether a visible destination is still Coming Soon.