See how a light distributes its output. Compare files side by side and save the results.
Photometric comparison
LEDYI Lighting · Data derived from the files listed below
Start with a photometric file
Choose a file to see its distribution and parameters, or explore the viewer with two examples.
Light distribution
Compare measured light intensity on the same scale.
Solid: C0–C180 · Dashed: C90–C270
0° = straight down · 180° = straight upSame cd scale for every file
Move across the curve
Estimate direct illuminance directly below each fixture, using its actual intensity at 0°. The files keep their original output.
E = I(0°) ÷ distance². Far-field estimate only; excludes reflections and obstructions. For long strips or close mounting, use application-distance measurements.
Compare the files
Values for the complete tested source
Beam = full width at 50% of that plane’s peak. Field = 10%. “—” means unavailable or no single bounded lobe.
Selected file: details & checks
Save chart ⌄
An offline copy includes your files and view settings. Send it to a colleague to open the same comparison.
Good to know
Should I compare intensity or shape?
Intensity · cd keeps all files on one candela scale, showing actual output in each direction. Shape · % divides every value by that file’s overall peak, so you can compare distribution without output dominating the plot. Normalizing the view never changes the file or the lumen values.
Are the lumens and watts for one metre of LED strip?
They describe the complete source used in the photometric test. An IES file does not guarantee “per metre” values. Check the measured length, power setting, CCT and optics against the supplier’s test report. Luminous dimensions describe the light-emitting area and may differ from physical product dimensions.
Why can source lumens differ from calculated output?
A relative IES file may list lamp lumens before optical losses. They are not necessarily the luminaire’s emitted output. This viewer integrates the intensity grid for emitted flux and labels the source value separately. In absolute IES photometry, −1 is a flag; it is not a measured lumen value.
Can this tell me if a room is bright enough?
The distance view is a direct, far-field estimate beneath one downward-pointing fixture. A complete design also needs mounting position, room surfaces, reflections and the calculation plane. Long LED strips at short distances need particular care. Use DIALux, Relux or equivalent design software for a room study.
How do I send this comparison to someone?
Use Save offline copy. It downloads one HTML file containing the source files, fonts and viewer, with the current selection and settings. It opens without an internet connection. Share only files you are authorised to disclose. SVG, PNG and CSV exports also carry sample labels where applicable.
How are results calculated, and what is checked?
File counts, numeric values, angle ordering and supported symmetry are checked before plotting. Values between measured angles use linear interpolation; luminous flux integrates that angular model over solid angle. LDT cd/klm is converted to cd from its reference flux and conversion factor. Calculated metrics are estimates from the sampled file data, not independent laboratory measurements. This viewer supports IES Type C with no TILT correction and single-set LDT. It does not certify a file, invent missing power or colour values, or compute UGR / lifetime reports from insufficient data. Read the IES format reference and EULUMDAT format reference.
Need photometry for your LEDYI configuration?
Tell us the model, tested length, power and CCT you need.
Read the tool instructions in Markdown and the request/response schemas in OpenAPI. These public calculation APIs run the same models as the web and offline calculators. No account, API key or Turnstile is required.
POST /api/tools/v1/photometry
Content-Type: application/json
Read Type C IES with TILT=NONE or single-lamp-set EULUMDAT text. Return file facts, integrated flux and full-width beam metrics, plus every requested intensity query in candela. This does not verify laboratory measurements or replace a lighting design study.
Photometry JSON bodies are limited to 1024 KiB, independently of the browser file limit. The parsed table is limited to 250000 cells per file; HTTP results include only the explicitly queried directions and full-file metrics, not a silent partial export of the native table.
photometry
IES / LDT photometric analysis
POST files as JSON-escaped text with explicit cPlanesDeg and gammaAnglesDeg arrays. Angles must be strictly increasing: C is in [0,360), gamma in [0,180]. Maximum 4 files, 16 C planes and 721 gamma angles per file. The sample is mathematical test data, not a LEDYI product.
The browser reads files locally; this API explicitly sends the supplied text to the server for stateless analysis. No external file URLs are fetched. Source text is excluded from response inputs and logs; no result is stored. links.share is null because source files are not encoded in URLs. Use Save offline copy for a local, restorable handoff. Compare tested source length, power setting, CCT and optics before drawing product conclusions. Values are not automatically per metre.
Request limits and errors
Send uncompressed application/json with strict types and no query parameters. Indoor lighting bodies are limited to 16 KiB; driver-match bodies to 16 KiB; battery bodies to 16 KiB; voltage bodies to 16 KiB; resistor bodies to 16 KiB; DMX bodies to 1024 KiB and 1000 fixtures; pixel bodies to 64 KiB, 64 run rows, 128 outputs and 2000000 channels. DALI bodies are limited to 64 KiB, 24 rows and 512 devices. Illuminance bodies are limited to 16 KiB and 400 planned points. Photometry bodies are limited to 1024 KiB with up to 4 files and 16 by 721 query directions per file. Lighting-cost bodies are limited to 64 KiB with up to 20 groups in each scenario. Body reading expires after 5 seconds. Complete success JSON is bounded to 4 MiB. GET/HEAD return 405; OPTIONS returns 204. Source responses are no-store. Anonymous browser CORS permits POST/OPTIONS and Content-Type with credentials omitted.
Tool POST requests and ordinary page requests share 120 requests per 60 seconds per IP/Cloudflare location; mitigation lasts 60 seconds. Heavy tool use can temporarily block pages from the same source. This is not an independent or globally exact API quota. Inquiry/search use their existing separate rule. Tool POST requests do not inherit the company-page or verified-bot exemption.
Cloudflare can return 403/429/5xx before the application, sometimes as HTML without CORS or Retry-After. Check HTTP status and Content-Type before parsing JSON. A browser may see only a network error. Do not present an error or an older result as a successful new calculation.