{"id":18963,"date":"2026-09-21T10:20:00","date_gmt":"2026-09-21T08:20:00","guid":{"rendered":"https:\/\/www.lukaswojcik.com\/blog\/?p=18963"},"modified":"2026-09-17T13:37:19","modified_gmt":"2026-09-17T11:37:19","slug":"mastering-streaming-loudness-fl-studio-2026-step-by-step","status":"publish","type":"post","link":"https:\/\/www.lukaswojcik.com\/blog\/en\/music-production\/tutorials-en-music-production\/mastering-streaming-loudness-fl-studio-2026-step-by-step\/","title":{"rendered":"Mastering to Streaming Loudness in FL Studio 2026: Parametric EQ 2, Maximus, Fruity Limiter and True Peak Step by Step"},"content":{"rendered":"

A finished mix becomes a master once loudness, peak level and export format are right. For streaming services, that means an integrated loudness that fits the service’s target and a true peak with enough headroom below 0 dBTP, so that encoding to AAC, Ogg Vorbis or Opus does not cause clipping. FL Studio 2026 includes the tools needed: Fruity Parametric EQ 2 for corrections, Fruity Limiter in all editions and Maximus from Producer Edition upwards as limiters, and the Analyzer module in FL Studio Mobile Rack, which shows loudness in LUFS and true peak.<\/p>\n

The tutorial follows Image-Line’s online manual as of FL Studio 2026.1.6. A measurement also shows how far a limiter without oversampling overshoots its ceiling and which ceiling masters between \u221214 and \u22128 LUFS need.<\/p>\n

\n\"Dot
True peak at a limiter ceiling of \u22121 dBFS, measured on the test mix without and with oversampling.<\/figcaption><\/figure>\n

Targets: \u221214 LUFS and a true peak below \u22121 dBTP<\/h2>\n

Spotify recommends an integrated loudness of \u221214 LUFS and a true peak below \u22121 dB for masters. For masters louder than \u221214 LUFS, the help page recommends a true peak below \u22122 dB, because louder tracks are more susceptible to extra distortion when encoded. At the Normal level, Spotify turns louder masters down to \u221214 LUFS and raises quieter ones only as far as 1 dB of headroom remains for the lossy formats. Normalization also applies to FLAC playback.<\/p>\n

AES TD1008 recommends \u221216 LUFS for music in streams with track normalization and \u221214 LUFS for the loudest track of an album with album normalization, plus no more than \u22121 dBTP at the codec input. With normalization switched on, a louder master therefore does not play louder, but it has less dynamic range and less headroom below 0 dBTP. How far AAC, MP3, Ogg Vorbis and Opus raise a master’s peaks is shown in the article True Peak After Encoding<\/a>.<\/p>\n

Which stock tools show loudness and true peak<\/h2>\n

FL Studio has no plugin called Loudness Meter. Three included tools show loudness in LUFS, and only one of them shows a true-peak reading:<\/p>\n\n\n\n\n\n\n\n\n
Tool<\/th>\nEditions<\/th>\nReadout<\/th>\n<\/tr>\n<\/thead>\n
Analyzer in FL Studio Mobile Rack<\/td>\nall<\/td>\nLOUDNESS tab with the modes LUFS 0.4s (Momentary), LUFS 3s (Short-term), RMS, Peak and True Peak, plus the values Peak, Integrated and Range<\/td>\n<\/tr>\n
Emphasizer<\/td>\nall<\/td>\nintegrated loudness in LUFS<\/td>\n<\/tr>\n
Emphasis<\/td>\nAll Plugins Edition only<\/td>\nMomentary, Short-term and Integrated loudness, plus true-peak limiting<\/td>\n<\/tr>\n
Wave Candy, Fruity dB Meter, mixer<\/td>\nall<\/td>\nlevels in dB; Wave Candy has a meter mode per ITU-R BS.1770, but the manual does not mention a LUFS readout<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

The Analyzer manual describes the Integrated value only as an average; whether it is calculated with gating as in BS.1770 is not documented. The values are reset by selecting another tab and then LOUDNESS again. For the final check, measuring the exported file is therefore the better choice.<\/p>\n

Measurement: how far a limiter without oversampling overshoots its ceiling<\/h2>\n

A limiter that only limits sample values holds its ceiling for the samples. Peaks between the samples, which are measured as true peak, can sit above it. The Fruity Limiter manual mentions neither true peak nor oversampling. In Maximus, the Oversample option switches on oversampling, with which, according to the manual, the compressor stages also respond to inter-sample peaks. Emphasis has a switch for true-peak limiting per EBU R 128 and oversampling up to 16 times.<\/p>\n

How large the difference can be is shown by a measurement with the synthetic test mix from the true peak article, which sat at \u221218.5 LUFS before mastering. ffmpeg’s alimiter served as the limiter, once directly at 44.1 kHz and once in a four-times oversampled signal path, as a stand-in for a limiter without and with oversampling. For each loudness target the gain before the limiter was readjusted, and true peak was measured per ITU-R BS.1770-5. Fruity Limiter and Maximus may give different values, but the measurement shows the order of magnitude.<\/p>\n\n\n\n\n\n\n\n\n\n\n
Target<\/th>\nWithout oversampling: true peak at \u22121 dBFS<\/th>\nCeiling needed for \u22121 dBTP<\/th>\nWith oversampling: true peak at \u22121 dBFS<\/th>\nCeiling needed for \u22121 dBTP<\/th>\n<\/tr>\n<\/thead>\n
\u221214 LUFS<\/td>\n\u22121.51 dBTP<\/td>\n\u22121.00 dBFS<\/td>\n\u22121.67 dBTP<\/td>\n\u22121.00 dBFS<\/td>\n<\/tr>\n
\u221212 LUFS<\/td>\n\u22120.82 dBTP<\/td>\n\u22121.21 dBFS<\/td>\n\u22120.95 dBTP<\/td>\n\u22121.08 dBFS<\/td>\n<\/tr>\n
\u221211 LUFS<\/td>\n\u22120.77 dBTP<\/td>\n\u22121.26 dBFS<\/td>\n\u22120.91 dBTP<\/td>\n\u22121.12 dBFS<\/td>\n<\/tr>\n
\u221210 LUFS<\/td>\n\u22120.73 dBTP<\/td>\n\u22121.30 dBFS<\/td>\n\u22120.88 dBTP<\/td>\n\u22121.15 dBFS<\/td>\n<\/tr>\n
\u22129 LUFS<\/td>\n\u22120.63 dBTP<\/td>\n\u22121.60 dBFS<\/td>\n\u22120.88 dBTP<\/td>\n\u22121.15 dBFS<\/td>\n<\/tr>\n
\u22128 LUFS<\/td>\n\u22120.29 dBTP<\/td>\n\u22121.98 dBFS<\/td>\n\u22120.88 dBTP<\/td>\n\u22121.15 dBFS<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

At \u221214 LUFS, a ceiling of \u22121 dBFS was enough in both cases. From \u221212 LUFS upwards, the true peak without oversampling sat above \u22121 dBTP, reaching \u22120.29 dBTP at \u22128 LUFS, and the ceiling had to drop as far as \u22121.98 dBFS. With oversampling, the true peak stayed at \u22120.88 dBTP or below, and \u22121.15 dBFS was enough for every target. Without oversampling, the gap between true peak and loudness shrank from 12.5 dB at \u221214 LUFS to 7.7 dB at \u22128 LUFS.<\/p>\n

A cross-check with 16-times oversampling separates the two cases even more clearly. Without oversampling, the peaks there were up to 0.39 dB higher than per BS.1770: even with the needed ceilings from the table, the masters from \u221212 to \u22128 LUFS reached \u22120.89 to \u22120.62 dBTP in the cross-check. With oversampling, the two measurements differed by no more than 0.03 dB. EBU Tech 3343 gives a possible under-read of about 0.5 dB for four-times oversampling meters; in this measurement it occurred only with the limiter without oversampling.<\/p>\n

Step 1: Setting up the master chain<\/h2>\n

The chain sits in the effect slots of the master track in the mixer. According to the manual, only the master track and tracks routed directly to an ASIO output can clip; peaks above 0 dB on the other mixer tracks are harmless. The chain in this tutorial, in slot order:<\/p>\n

    \n
  1. Fruity Parametric EQ 2<\/strong> for corrections, for example a high pass with the Steep 4 slope (\u221224 dB per octave) against rumble, or a low shelf. The LIN switch puts all bands into linear phase and adds latency in return. According to the manual, inter-sample peaks can raise the output peaks in HQ L mode.<\/li>\n
  2. Optionally a compressor or clipper, such as Fruity Multiband Compressor, Fruity Soft Clipper or Emphasizer.<\/li>\n
  3. The limiter as the last effect that changes the level: Fruity Limiter, Maximus or Emphasis.<\/li>\n
  4. After it, FL Studio Mobile Rack with the Analyzer module, so that the meter measures the signal after the limiter.<\/li>\n<\/ol>\n

    Step 2: Setting up Fruity Limiter<\/h2>\n

    Fruity Limiter is included in all editions. Inside the plugin, compressor, gain, limiter with noise gate and saturation follow one another; for mastering, the LIMIT<\/strong> tab is what matters.<\/p>\n

      \n
    1. CEIL<\/strong> sets the ceiling. For a master around \u221214 LUFS, \u22121 dB was enough in the measurement. Louder masters need a lower ceiling with a limiter without oversampling: for \u22121 dBTP, about \u22121.3 dB at \u221210 LUFS and \u22122 dB at \u22128 LUFS. For the \u22122 dBTP that Spotify recommends, a master at \u22129 LUFS needed a ceiling of \u22123.0 dB in the same test mix.<\/li>\n
    2. GAIN<\/strong> raises the level before the limiter. It goes up step by step until the Analyzer shows the desired short-term loudness in the loudest passage.<\/li>\n
    3. ATT<\/strong> sets how quickly the limiter responds and at the same time sets the look-ahead delay; at 0 ms there is none. REL<\/strong> sets how the level returns, and CURVE<\/strong> shapes attack and release together.<\/li>\n<\/ol>\n

      The SAT<\/strong> control sets the saturation threshold: the further left it is turned, the more the plugin saturates.<\/p>\n

      Step 2 with Maximus or Emphasis<\/h2>\n

      Maximus is included from Producer Edition upwards and has no threshold knob: the threshold and curve of each band are set by an envelope drawn in the plugin. The Default patch sets all bands to hard limiting. In the Options menu, Oversample<\/strong> switches on oversampling, with which the compressor stages also respond to inter-sample peaks. The 0.2 dB compressor safety<\/strong> option keeps an extra 0.2 dB of headroom. The CEIL control in the saturator is a soft saturation ceiling, not a limiter ceiling; the level after compression is set by the POST gain. The attack time of the MASTER band also sets the look-ahead and therefore the latency.<\/p>\n

      Emphasis is included only in the All Plugins Edition. There, Output<\/strong> sets the output ceiling in dB, the True Peak<\/strong> switch activates true-peak limiting per EBU R 128 with oversampled peak analysis, and Oversampling<\/strong> ranges from Off to 16x. If the project runs at 192 kHz, the manual says the plugin’s oversampling should stay off.<\/p>\n

      Step 3: Reading loudness and true peak in the Analyzer<\/h2>\n
        \n
      1. In the Analyzer module, the LOUDNESS<\/strong> tab shows the loudness measurement.<\/li>\n
      2. The LUFS 3s<\/strong> mode shows short-term loudness, the LUFS 0.4s<\/strong> mode momentary loudness.<\/li>\n
      3. In True Peak<\/strong> mode, the Analyzer also shows the peaks between samples, which according to the manual it determines by interpolation; the Peak value gives the maximum.<\/li>\n
      4. The track plays through once completely before Integrated and Range are read. Target only sets a visual marker.<\/li>\n<\/ol>\n

        Step 4: Exporting<\/h2>\n