In OBS Studio, extra encoder parameters go in the custom-options field for the streaming encoder, when that encoder exposes one. The field’s location and accepted syntax depend on your OBS version and selected encoder, so there is no single string you can safely copy between NVENC, x264, AMD AMF, Quick Sync and FFmpeg modes.
Start by checking what OBS is actually using, then consult documentation for that encoder before changing anything. Add one supported option at a time, test the stream, and keep a record so you can remove a change that causes trouble.
What extra encoder parameters do
An encoder takes your video and audio and prepares them for the stream. OBS gives you ordinary controls for common choices such as bitrate, rate control, codec and keyframe interval. Extra encoder parameters are a way to pass additional encoder-specific properties when the interface offers a custom field.
That does not make the field a general-purpose place to enter any setting you have seen in a tutorial. A property may exist only for one encoder, may require a particular value format, or may be meaningful only with a certain rate-control mode. A valid option can also be a poor choice for your service or hardware. Treat a custom field as a narrow interface to the selected encoder, not as a universal “advanced settings” box.
Before using it, ask what problem you are trying to solve. If you need to change bitrate or keyframe interval, first look for the normal OBS control. A custom option is more appropriate when the relevant property is not exposed in the interface or encoder documentation specifically calls for it. If there is no clear reason for the change, leave the field empty.
OBS maintains separate encoder implementations and compatibility notes. Its hardware encoding guide describes which hardware encoder paths are available on different systems; the advanced recording settings guide is a useful illustration of how baseline choices differ by encoder. That second guide concerns recording, however, so do not treat its recording recommendations as a live-stream prescription.
The destination matters as well. A streaming service may have requirements for codec, keyframe behaviour, bitrate or other output characteristics. Check the service’s current official guidance before adopting an encoder vendor’s example. A setup that is technically accepted by an encoder is not automatically appropriate for your channel.
Check OBS mode, encoder and version
Open Settings → Output in OBS. If the Output Mode is set to Simple, switch to Advanced to see the streaming encoder controls discussed here. Check the Streaming tab and note the encoder currently selected; do not infer it from your graphics card or from an old setup guide.
Write down your OBS version, operating system, selected encoder, codec if shown, relevant hardware, and streaming service. For instance, “OBS version, Windows, NVIDIA NVENC, H.264, YouTube” gives you a much more useful reference than “my stream settings”. You will need that information if you consult documentation, ask for help or return to the previous setup.
The encoder choice may change what fields appear. An NVIDIA encoder is not interchangeable with AMD AMF, Intel Quick Sync, Apple VideoToolbox, x264 or an FFmpeg output path. Availability also depends on the computer and its supported hardware and software. If your encoder is missing, consult OBS’s compatibility information rather than trying to make a custom option for another encoder fit.
Keep the target service in the picture. YouTube’s requirements and accepted formats can differ from those of another platform, and platform guidance can change. OBS and NVIDIA explain encoder behaviour; YouTube remains the source to check for YouTube’s current requirements. Do not copy a recommendation for another service just because it was written for the same encoder.
This identification step also helps you decide whether a custom option is needed at all. OBS’s normal controls cover many routine streaming choices. If you cannot explain what the proposed property changes, or cannot find it in documentation for your active encoder, do not add it just because a forum post or video includes it.
Find the custom-options field
With Output Mode set to Advanced, open the Streaming section under Settings → Output and select the encoder you intend to use. Expand its settings if necessary. Look for a field labelled for custom options or additional encoder options; the exact label and whether it is present vary by encoder and OBS version.
If there is no such field, do not paste the option into another box, such as a bitrate field, and do not assume a field shown in an online screenshot will exist in your installation. Check that you are looking at the Streaming output settings rather than Recording, and verify the encoder selection. If the field remains absent, the selected path may not expose custom options in that version of OBS.
For NVIDIA NVENC, OBS documents its advanced custom properties for OBS 31.0 and later. The OBS Project’s Advanced NVENC Options page explains both the field syntax and individual supported properties. Earlier versions may not display the same options, so compare your installed version with the page rather than following its instructions by appearance alone.
OBS’s interface for AMF and FFmpeg also describes a custom-options field, but that does not mean NVENC properties work there. A box with a similar purpose is not proof that two encoders accept the same names, values or behaviour. Read the documentation for the exact implementation you have selected.
Before editing, take a screenshot or note the existing output settings. Keep a copy of any current custom text, even if the field is empty. That gives you a clear rollback point and avoids relying on memory when you are trying to diagnose a failed output later.
Use encoder-specific option syntax
Syntax is part of the setting. OBS’s NVENC documentation for version 31.0 and later describes custom properties as option=value pairs separated by spaces. That describes how to write supported NVENC properties in that field; it does not mean every word before or after an equals sign is recognised, nor that the same spelling works in another encoder’s box.
The OBS AMF/FFmpeg interface text likewise describes an option=value format and includes level=5.2 profile=main as an example. It is an example of syntax, not a recommended live-stream string and not evidence that those values are right for your setup. Follow the documentation for your selected encoder and check both spelling and value format.
NVENC’s option list illustrates why a source matters. OBS documents keyint as a keyframe interval in frames and explicitly says it is not a standard NVENC option. Its documentation also describes gopLength, with a note to use keyint except for the special infinite-GOP case. Those details belong to OBS’s NVENC handling; they are not instructions to use either name with x264, AMF or another encoder.
Some properties only apply in a particular rate-control mode. For example, OBS lists NVENC rate-control properties such as averageBitRate and maxBitRate; whether a property is appropriate depends on the mode and the rest of your configuration. Prefer the normal OBS controls when they cover the choice you need, and consult the current property list before adding an extra one.
A useful way to compare candidate options is by asking what they touch and what could be affected:
| Check | Why it matters |
|---|---|
| Encoder and platform | An option may exist only for a particular implementation or supported hardware and operating system. |
| Codec and service | The encoder may support a format that your streaming destination does not accept or recommend. |
| Rate control and bitrate | Some properties only apply in a particular mode; changing them can conflict with ordinary output controls. |
| Keyframe or GOP behaviour | A value may be expressed in frames or serve a special use, and the service may have its own requirements. |
| CPU or GPU load | Encoder choices have different resource demands; watch your actual system rather than assuming a performance gain. |
| Quality at your bitrate | The effect depends on content and available bitrate, so judge the resulting stream on your own material. |
NVIDIA’s NVENC OBS guide offers recommendations for a specific NVIDIA workflow. Read those as vendor guidance for the described workflow, not as universal OBS settings or a substitute for your service’s requirements. Do not change a setting simply because it appears in a polished example; first confirm the encoder, output goal and current platform guidance match your situation.
Add one option at a time
Make a small, reversible change. Begin with a working configuration and change only one property, using the exact name, separator and value format in the selected encoder’s documentation. Keep a note of the original value and the reason for the change. If a guide proposes a long string, break it into individual properties and check each one before considering it.
Do not combine several untested options in one edit. If output stops or quality changes, a bundle makes it difficult to identify which property caused the result. A one-change-at-a-time process gives you a useful comparison: the same scene, source material, service and approximate viewing conditions before and after the change.
Prefer an OBS control for familiar settings such as bitrate, rate control and keyframe interval when it is available. The custom field is not a reason to bypass a control that OBS already presents. This matters especially when one setting might override, duplicate or conflict with another setting in the interface.
For a live channel, use a controlled test before relying on the change through a long broadcast. Check that OBS starts the output, that the service receives it, and that the picture and sound behave as expected. A successful start alone does not establish that the option improved anything. If you cannot identify a concrete benefit in your own output, there may be no reason to keep the extra complexity.
Keep the use case in view. A devotional channel with a static image, a lofi stream with moving artwork, a local news loop and a study channel can put different demands on the encoder. The right choice depends on the source, encoder, available compute and destination requirements; a setting that seems reasonable for one scene is not a general rule for another. For planning the rest of a continuous broadcast, see how to livestream pre-recorded videos on YouTube 24/7.
If your problem is that a broadcast must continue while your own computer is switched off, that is separate from choosing encoder options in OBS. StreamNeo can remove the need to keep that computer running for an uploaded-video YouTube stream; it does not make an unverified OBS parameter safe or universal. Keep encoder decisions tied to the setup that will actually produce your output.
Test output and check logs
After editing, apply the setting and start a test output if your workflow allows it. Some changes may require the output to be stopped and started, or the encoder to be reinitialised, before they take effect. Do not assume the value has been accepted merely because it remains visible in the field.
Watch OBS’s status indicators and review its log after the test. Look for encoder errors, warnings or output failures around the time you applied the change. The log can help show whether OBS could initialise the encoder, but it cannot by itself prove that a setting is right for your service or has improved the picture. Pair it with a check of the actual stream and the service’s status.
Check the kinds of symptoms that relate to the change: whether the stream starts, whether video and audio continue, whether the image appears as expected, and whether the computer shows a resource problem. Compare like with like where possible. A scene change, network fluctuation or different source clip can make a before-and-after judgement unreliable.
If the output is for YouTube, review the stream in the way your audience will see it and check YouTube’s current live-streaming guidance. OBS logs and a local preview are useful, but the destination may identify issues that are not obvious in the OBS interface. Do not treat a clean log as proof of compliance or guaranteed acceptance; check current official requirements yourself.
You can also consult the OBS guide to continuous-stream options when deciding whether a computer-based OBS workflow suits a channel that should run around the clock. That decision is different from validating a property in the custom-options field. Whatever workflow you use, record which configuration you tested and what you observed so that a later change is not confused with this one.
Remove options that cause problems
If OBS fails to start the encoder, the stream behaves differently in a harmful way, or you cannot verify the change, remove the last option you added. Restore the recorded setting or clear the custom-options field, then restart or reinitialise the output and confirm that the previous behaviour returns. Avoid adding a second option in an attempt to compensate for a first one you do not understand.
An error can come from a misspelling, unsupported property, invalid value, incompatible encoder, version difference or an interaction with another control. Check the log and the documentation again, but do not guess at alternative spellings. If the property is not listed for your selected encoder and version, treat it as unsupported until you find authoritative documentation that says otherwise.
Keep a simple change record: date, OBS version, encoder, option added or removed, reason, and test outcome. When you update OBS or change hardware, revisit the custom properties rather than assuming they remain suitable. A configuration that worked on one encoder or driver may not carry over after changing the active output path.
For a channel that depends on a predictable loop, stability is often more useful than an unproven tweak. You may find it more helpful to check how video order is preserved in a YouTube loop than to add encoder properties unrelated to the actual problem. Keep the output configuration as simple as you can while meeting the documented requirements for your encoder and service.
Before committing, compare the operating options on the pricing page. When the file and channel are ready, start free — 24-hour trial, no card.
FAQ
How do I set extra encoder parameters for streaming?
In OBS Studio, switch Output Mode to Advanced, select the streaming encoder and look for its custom-options field. Use only properties documented for that exact encoder and version, then test the output and check the log before relying on the change.
Where do I put custom encoder options in OBS?
Look under Settings → Output → Streaming after choosing Advanced output mode and the encoder you intend to use. The field may not be available for every encoder or OBS version, so do not paste a setting into a different field if you cannot find it.
What syntax does the OBS encoder options box use?
It depends on the encoder. OBS documents space-separated option=value pairs for its NVENC custom options in OBS 31.0 and later; check the relevant OBS documentation for your selected encoder rather than assuming that format or the same property names apply everywhere.
Can I use the same encoder parameters with NVENC and x264?
Do not assume so. NVENC and x264 are different encoder implementations, with their own options and behaviour; use the documentation for the one OBS shows as active and verify the result on your own output.