FWHM helps define how wide a bandpass or narrowband filter window should be, but it needs the center wavelength, transmission and blocking fields around it.
Prepare FWHM fields for optical filter review with wavelength, bandwidth, blocking, geometry, product-family path, and RFQ checklist guidance.
FWHM belongs in the first technical description because it shapes how an optical filter request is reviewed. Use the field to describe the intended spectral position, width, blocking need, geometry, or transmission context before asking for a drawing review or quotation.
Add the field to the technical RFQ package before sending drawings or spectra.
A clear value helps separate a general component search from a request that can be checked against filter family, wavelength band, coating context, substrate, and size constraints. When the value is uncertain, state the acceptable range or the measurement condition instead of forcing a single number.
Prepare known values, acceptable ranges, and measurement conditions.
Useful request notes include the target band or wavelength, bandwidth or blocking target, AOI, substrate, outside dimensions, quantity, application context, and any drawings or spectra that explain the optical path. Keep commercial timing separate from the technical fields so the first review can focus on feasibility.
List target values and attach supporting spectra when available.
Review the product family that matches the optical function first: bandpass filters for passband selection, longpass or shortpass filters for edge behavior, dichroic optics for beam splitting, neutral density filters for attenuation, and coated optics when the geometry or substrate is the main constraint.
Open the relevant product family, then return to the RFQ package.
Write the field as a technical note rather than a sales summary. Include what is fixed, what can be adjusted, what documents are attached, and which application context matters most. This keeps the inquiry useful without asking the buyer to make unsupported performance assumptions.
Send the checklist with application context, target values, and document needs.
A buyer can ask for product sheets, coating review notes, drawing review, or spectrum-related documents when those materials are needed for evaluation. The request should describe the project context and the exact document type needed so Lumalyx can route the response for technical review.
Ask for the document type needed and include the related field values.
Use these fields to turn the page topic into a reviewable Lumalyx request.
FWHM is commonly used to describe the width of a spectral pass band around its center wavelength.
A wider or narrower band changes how much useful signal passes and how much adjacent wavelength content may enter the path.
Pair FWHM with CWL, transmission target, blocked range, OD target and the instrument path that uses the filter.
For many bandpass and narrowband filters, FWHM is the width measured at half of the maximum transmission level. In practical sourcing language, it helps reviewers understand how tight or broad the desired signal window should be around the center wavelength.
Use FWHM with CWL instead of sending a bandwidth value alone.
A narrower window can help isolate a signal, while a broader window may support higher useful transmission or a wider source spectrum. The right discussion depends on the signal, detector, neighboring wavelengths and acceptable background level.
Include the source, detector and nearby channel context when available.
Send CWL, target FWHM or pass band edges, minimum transmission target, blocked range, OD target, AOI, substrate, size and any spectra. If the request is part of a multi-channel set, include the other channels too.
Open an RFQ when you can name the signal path but not every numeric value.
FWHM is often central to fluorescence and narrowband filter discussions. It may also appear in analyzer, sensing or laser-path work where a controlled spectral window is needed.
Move to the fluorescence bandpass family or prepare a technical RFQ.
These fields make the request easier to evaluate and show which values are confirmed, approximate or still open.
Send the values you know, mark uncertain fields clearly and include spectra, drawings or existing references when they help explain the signal path.
Start technical RFQFWHM is most useful when the request also names the center wavelength, blocked bands and the reason the pass window needs to be wide or narrow.
| Field | Send when | Review note |
|---|---|---|
| CWL | The pass band has a known center. | CWL anchors the bandwidth discussion. |
| FWHM | The signal window width is known or can be estimated. | Use a target range if the exact width is open. |
| Adjacent channels | Nearby wavelengths may enter the detector path. | Include neighboring bands or spectra. |
A narrow FWHM does not automatically resolve a signal-path problem without blocking and geometry context.
Localized FWHM pages should be created only after regional searches show a different engineering vocabulary or RFQ pattern.
Send source, detector, pass-band and blocked-band context together when bandwidth is the main question.
These answers keep the request focused on reviewable engineering fields.
FWHM describes the width of a pass band at half of its maximum transmission level. Buyers often use it to express how narrow or broad the signal window should be.
For bandpass and narrowband requests, both are useful. CWL anchors the center, while FWHM describes the working width around it.
Yes. Pass band edges, a target spectrum or an application channel list can help the review identify the needed bandwidth discussion.
