For a mostly static jewellery showroom shot with occasional, deliberate hand movement, start with OBS at 1920×1080, 30 fps, H.264, CBR and a 2-second keyframe interval. Use 5,000 Kbps as the video-bitrate starting point, with AAC stereo audio at 128 Kbps and Rec. 709 SDR, then lower the video bitrate if a real upload test and stream-health check show that your connection cannot sustain it.
That profile is a practical starting point based on YouTube’s encoder guidance, not an India-wide best preset or a guarantee of stable streaming at 5,000 Kbps. Your usable upload capacity, other traffic on the connection, computer load and the amount of motion in the shot all matter. Test the actual scene and route before you rely on the stream overnight.
Start with the kind of showroom shot you have
A fixed camera pointed at a display counter has different demands from a presenter who walks around the shop. If the frame mostly contains a still background and products, with a hand entering occasionally to turn a ring or lift a necklace, 30 frames per second is a reasonable first choice. It captures that deliberate movement without asking for the same data rate as a higher-frame-rate profile.
Jewellery can be demanding in a different way: polished metal, small engravings and facets may look soft when the picture is compressed. Increasing bitrate can preserve more detail, but only if the connection can carry it consistently. A brief sharpness improvement is not useful if the stream repeatedly buffers or drops frames.
Prepare the shot as well as the encoder. Keep the display and background consistent, avoid abrupt changes in lighting, and, if your camera allows it, lock exposure and white balance after the scene is set. Try the actual pieces you intend to show: a matte item and a reflective item may look different under the same light. Move a product slowly enough that viewers can see its finish and colour. These are production suggestions, not YouTube-prescribed jewellery settings; if exact colour representation matters to a sale, check the camera and display workflow separately.
If the stream is a loop made from a prepared product video rather than a live camera, check the source file too. The practical steps in preparing a video for a 24/7 YouTube loop help you avoid treating an encoding setting as a fix for problems already present in the video.
Set resolution and frame rate
For a close showroom view where product detail matters, begin at 1920×1080 output and 30 fps. In OBS, set both the base canvas and output resolution deliberately; if they differ, OBS has to scale the picture. Check that the camera or source is framed for the chosen canvas, so the product is not cropped or stretched.
YouTube’s H.264 guidance recommends 5 Mbps for 1080p30 and 3 Mbps for 720p30. Those are platform recommendations, not measurements of your connection. The lower 720p30 option can be a sensible fallback if the 1080p profile cannot remain healthy after testing. It trades some visible detail for a lower recommended video bitrate and may also reduce the work your computer does, depending on the source and encoder.
| Output profile | YouTube H.264 recommended video bitrate | When to consider it |
|---|---|---|
| 1080p30 | 5 Mbps | Start here when close-up detail matters and upload capacity is stable |
| 720p30 | 3 Mbps | Try this when 1080p30 is not sustainable or the encoder struggles |
| 1080p60 | 12 Mbps | Consider only if smoother movement is visibly useful and the connection and computer can support it |
| 720p60 | 6 Mbps | A higher-motion alternative where 60 fps is useful, subject to the same capacity checks |
These figures come from YouTube’s encoder settings, bitrates and resolutions guidance. They describe recommended H.264 bitrates for the listed profiles; they do not tell you what your internet service will sustain. For a static counter display, there is usually a stronger reason to prioritise reliable 30 fps than to choose 60 fps simply because the option exists. If your presenter regularly moves products quickly and the movement looks distracting at 30 fps, test 60 fps as a separate profile rather than changing it in the middle of a broadcast.
Configure H.264, CBR and keyframes
In OBS, choose H.264 for the video encoder if it is available and appropriate for your setup. Use CBR, or constant bitrate, as the rate-control mode. CBR aims to keep the encoded data rate steady; this makes it easier to plan around the upload capacity than a mode that allows the bitrate to vary substantially. It cannot make an inadequate or fluctuating connection reliable.
Set the keyframe interval to 2 seconds when the encoder exposes the control. At 30 fps, that interval corresponds to 60 frames. YouTube recommends 2-second keyframes and says not to exceed 4 seconds. OBS labels and available fields can vary with the selected encoder, so check the current YouTube requirement and your encoder’s controls rather than assuming every field appears in the same place.
Use the YouTube service and RTMPS endpoint in OBS where available, and paste the stream key from the correct YouTube event. Treat that key like a password: do not include it in screenshots, recordings or messages. YouTube’s encoder guidance also lists progressive scan, square pixels, two B-frames and one reference frame among its advanced recommendations when those controls are exposed. Avoid changing less familiar advanced fields by guesswork; first get the basic profile working, then confirm that your encoder is producing a compatible stream.
Choose a bitrate from measured upload
The 5,000 Kbps recommendation is a starting target for 1080p30, not an instruction to force that rate on any connection. OBS’s troubleshooting guidance suggests beginning around 75% of total upload speed. Applying that rough rule, a 5 Mbps video target implies about 6.7 Mbps of measured upload capacity before allowing for other traffic or variation. That is arithmetic from OBS’s rule, not a guarantee that a connection measured at that speed will sustain a live stream.
Run an upload test on the same connection you will use for the broadcast, at a time when the shop’s normal devices are active. A single test result is only a snapshot. Other people using the connection for video calls, cloud backups or file uploads can leave less capacity for OBS, and wireless conditions can change. Leave headroom rather than setting the encoder right up against the test result.
If 1080p30 at 5,000 Kbps produces dropped frames or unhealthy stream status, reduce the video bitrate and test again. You can try the 720p30 profile at YouTube’s 3 Mbps H.264 recommendation, or reduce further if the route still cannot sustain it. The right choice is the highest profile that remains reliable under your actual conditions, not the highest number OBS will accept.
This is a useful distinction for a showroom: bitrate affects encoded picture detail, while resolution describes the output dimensions. You can lower bitrate without changing resolution, but the picture may become more visibly compressed, especially on reflective close-ups. If you lower both resolution and bitrate, compare the result on a phone and a larger display before deciding that the trade-off is acceptable to your viewers.
Set AAC audio and Rec. 709 SDR
For a showroom promo with spoken product descriptions or quiet background music, set audio to AAC stereo at 128 Kbps and 44.1 kHz where the controls are available. YouTube lists AAC or MP3, stereo audio at 128 Kbps and a 44.1 kHz stereo sample rate in its encoder guidance. Check the microphone level and listen to the preview with headphones: a technically correct audio setting cannot fix a noisy microphone, clipping or music that masks speech.
Choose Rec. 709 for SDR colour and use 8-bit SDR unless you have deliberately built and tested an HDR workflow. The simpler SDR choice avoids introducing a colour pipeline you have not verified. Jewellery colour is commercially important, but choosing Rec. 709 does not guarantee that a piece will look identical on every viewer’s screen. Camera white balance, lighting, display settings and the viewing device all influence what people see.
Do not alter several colour controls at once to chase a vivid preview. Record a short test, check it on another display, and compare the item with what you see in person. If colour accuracy is essential to your listing or sale, validate the actual camera-to-screen workflow rather than treating a streaming preset as colour certification.
Test upload and stream health before going public
Create an unlisted or otherwise non-public rehearsal, then use the same camera, lighting, overlays, audio and product handling you expect to use live. YouTube advises testing with similar movement and audio before the event and monitoring stream health and messages during a broadcast. Let the rehearsal run long enough to expose the kind of variation you would miss in a brief setup check.
Check two views of the problem. In OBS, watch the dropped-frame counters and any encoder warnings. In YouTube’s live control room, watch stream health and messages. OBS explains that dropped frames indicate an unstable connection or one that cannot sustain the bitrate; a healthy preview at the start is not proof that the route will remain healthy. OBS recommends a wired connection for streaming, so use Ethernet if practical. Wired networking can reduce one source of variability, but it does not repair a weak or congested internet service.
Also verify what a viewer will actually see. Open the channel or watch page on a phone and check framing, audio and overlays. If you plan to keep a local recording, check that OBS is recording and that the file is growing. The guidance in keeping an OBS stream running overnight on a spare PC is useful if your workflow depends on a local machine remaining involved throughout the broadcast.
A continuous promo also raises a separate question: whether the live session and its archive should run without a break. YouTube says streams under 12 hours can be automatically archived, but a stream longer than 12 hours may not be captured at all. If the recording matters, plan sessions shorter than 12 hours and keep a local backup. YouTube also notes that DVR pause and rewind may be limited or unavailable on streams longer than 12 hours, which matters if late-arriving viewers need to go back to an earlier product demonstration. See YouTube’s archive guidance and test the DVR behaviour you need before relying on it.
Adjust after a real test, one change at a time
If OBS reports dropped frames, first check whether the bitrate is within the stable upload capacity you measured. Lower the bitrate and run the same test again; if needed, reduce output resolution to 720p30. Check whether other devices are using the connection, and prefer Ethernet over Wi-Fi if available. OBS also lists VPNs, security software and network hardware among possible contributors to connection trouble. Do not assume that buying a cable, changing a single router setting or restarting OBS will solve every case.
If the picture stutters while OBS reports encoder overload, the bottleneck may be the computer rather than the upload route. Try a lower output resolution or frame rate, or choose an encoder the computer can sustain, then rehearse again with the real scene. There is no universal CPU or GPU threshold that identifies a safe configuration for every machine. A static camera scene may be light work on one computer and difficult on another because of scaling, filters, overlays or simultaneous recording.
For a promo that should continue when the shop computer is switched off, StreamNeo removes the need to leave OBS running locally: you upload the finished video once and connect your YouTube stream key, while the cloud-run broadcast is monitored and restarted automatically if it drops. It is YouTube-only, so this is relevant when the source is a prepared video and you do not need a live camera or other platform; OBS remains the practical choice when you need hands-on scene control or live switching.
Keep a short record of each successful test: resolution, frame rate, bitrate, connection type, OBS counters and YouTube health messages. Change one variable per rehearsal so you can tell whether a lower bitrate, different resolution or altered encoder setting made a difference. For more on designing a repeatable loop, setting FFmpeg to loop a video for YouTube Live covers a different workflow; whichever method you use, verify the actual output rather than relying on a setting alone.
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
Is 5,000 Kbps a safe bitrate for every Indian connection?
No. It is YouTube’s recommended H.264 video bitrate for 1080p30, not a promise about any internet connection in India. Measure upload on the connection you will use, leave room for other traffic and lower the bitrate or output profile if stream health shows trouble.
Should I use 60 fps to make jewellery look sharper?
Not by default. Frame rate affects how motion is represented; it is not a general sharpness control for a mostly still counter shot. YouTube’s recommended H.264 bitrate is higher for 1080p60 than for 1080p30, so test 60 fps only if smoother product movement is visibly useful and your connection and encoder can sustain it.
Will a long continuous stream always be archived?
No. YouTube says a stream longer than 12 hours may not be captured at all, and DVR features can be limited or unavailable on streams over that duration. If you need an archive or rewind, plan shorter sessions, test DVR and keep a local recording as a backup.
What should I change first if the stream drops frames?
Check the upload route and bitrate before changing several OBS settings at once. Lower the bitrate, prefer a wired connection where practical, and repeat the same test while watching OBS’s dropped-frame counters and YouTube stream health. If the encoder rather than the network is struggling, test a lower resolution or frame rate.