Your Kick stream is only 720p, and your OBS settings are not the reason

# The list a capped channel actually gets

Kick published a page about this on 6 July 2026, and it is short enough that most guides have not caught up with it. Under the heading “What this means for your channel” it reads: “Some growing channels may currently have access to the following livestream resolution options:”, and then gives six of them — 720p60, 480p, 360p, 160p, Audio only and Auto.^[1] There is no 1080p entry, and the list is not presented as a fault. It is what the channel has, for now.

Two details in that list are worth pausing on, because they tell you something the rest of the page does not spell out. The first is 160p. A 160p rung is not something an encoder produces as a side effect of sending 1080p; it exists because something on Kick's side is re-encoding the feed into smaller versions. The second is Audio only, which is the bottom of the same ladder. So the widely repeated line that Kick does no transcoding and every viewer watches your source is not what Kick's own documentation describes. A capped channel is being transcoded; it is being transcoded into a ladder whose top rung is 720p60.

Where you see the list depends on the surface: in the web player it is the quality control on the stream, and the same set governs playback of the VOD afterwards. Kick describes the options as belonging to the channel rather than to a particular player, and says the limit reaches VODs as well as the live stream.^[1] Which control on which device exposes them is an inference from that, not something Kick documents surface by surface.

# Two layers people treat as one

Almost every wrong answer to this question comes from collapsing two separate limits into one number. Ingest is what your encoder pushes to Kick. Playback is what Kick hands to a viewer. They have different limits, set by different things, and only one of them is capped here.

Kick's streaming guide is explicit about the ingest side and has not changed: a maximum resolution of 1920x1080, a maximum of 60 fps, a bitrate of 1,000 to 8,000 kbps, CBR only — “Unfortunately not” is the whole answer to whether variable bitrate is supported — and H.264 rather than H.265.^[2] None of that is reduced while your channel waits for 1080p. You keep sending the same 1080p60 feed you were sending before, and Kick keeps accepting it.

This is also why the usual quality checklist misfires here. Upload speed, wired versus Wi-Fi, CPU load, encoder preset and dropped frames are all real causes of a bad stream, and Kick documents them properly in its lag guide.^[3] Every one of them degrades what you send. None of them adds a rung to the playback ladder.

# What Kick says unlocks it, and what it does not say

Kick's wording on the unlock is consistent and deliberately unquantified. 1080p “may become available once your channel reaches the required engagement threshold”; access is “managed automatically and becomes available once your channel meets the required engagement threshold”; and resolution availability is managed “based on your channel’s growth and engagement, so there are no settings you need to update”.^[1] Three statements of the same idea, and not one number among them.

One number does appear on that page, and it is the one most likely to be misread. Kick writes that as your channel continues to grow, the next milestone is reaching a 75+ average CCV, and that reaching it along with other requirements puts you on the path to becoming a verified creator.^[1] Read carefully, that sentence is about verification, not about 1080p. It sits in the same paragraph, which is what makes it easy to read as “1080p unlocks at 75 average CCV”.

The practical consequence is dull but useful: there is nothing to apply for. Kick says the availability is managed automatically and there are no settings to update,^[1] which means a support ticket asking for 1080p is asking a human to override an automatic system. If your channel is well past any plausible threshold and the options still stop at 720p60, that is the one case where contacting Kick support makes sense — as a bug report with your username, dates and a screenshot of the quality list, not as a request.

# The viewer number that is not in Kick's docs

Search this problem and you will meet a specific figure: that an average of two concurrent viewers is what unlocks 1080p, described as a guard against empty channels streaming around the clock and consuming bandwidth for nobody. It is the single most-repeated claim in the results for this question, and it is worth being precise about its status.

It is not in Kick's documentation. The page that carries the resolution list names no viewer figure at all for 1080p, and the only number on it is the 75+ average CCV milestone tied to verification.^[1] The guide page that the figure traces back to did not serve to us on 20 September 2026 — it answered with an HTTP 403 — so we can report that the claim circulates and where it points, but not that we read it on a live page this run.^[6] Nothing here says the figure is wrong. It says it is undocumented, and that is a different thing from confirmed.

• If it is true, almost every channel with a real audience clears it, and it explains nothing about a channel that has fifty viewers and still no 1080p.
• If it is stale, it may describe a rule that existed before Kick's July 2026 page and has since been replaced by an unpublished engagement measure. Kick's own phrasing — growth and engagement — suggests more than one input.
• Either way, it is not something to act on. There is no version of this rule under which the correct response is changing a setting, because Kick has already answered that question in the negative.^[1]

# If you are the viewer, not the streamer

The same cap reaches the other side of the screen with none of the explanation attached. You open a channel, the picture looks soft, you go into the quality control expecting 1080p and get a short list that stops at 720p60 — or, on a stream being watched on a small screen, apparently one option and Auto. The instinct there is to blame the connection, the browser or the device.

It is none of those. The resolution options belong to the channel, not to you.^[1] No browser change, app reinstall, cache clear or faster connection adds a rung that the channel does not have. The quick test is to open a large channel in the same browser on the same network: if 1080p appears there and not on the small channel, you have your answer in about fifteen seconds.

One thing the cap does not explain is chat, playback stalls or a stream that keeps buffering at any resolution. Kick handles those separately, and its lag guide points at upload stability, bitrate and dropped frames on the streamer's side.^[3] A soft picture with a short quality list is the cap. A picture that freezes and resumes is not.

# The mobile app has a different list

Kick's mobile broadcasting app, KICK - Go Live, publishes its own resolution list and it is not the same one. The app supports 240p on Android only, then 360p, 480p, 720p described as standard HD, and 1080p described as full HD, with a maximum bitrate of 8,000 kbps.^[4] That list is what the phone can send.

Seeing 1080p offered in the app is therefore not evidence that your channel has 1080p playback. It means the app will encode and send at 1080p, exactly as OBS does on a desktop, and the same channel-level cap applies to what viewers then get. The two lists live at different layers, and the app makes no claim about the second one.

• Choosing 1080p in the app when your connection is weak costs you battery, heat and stability for a resolution viewers may not receive anyway. Kick's own guidance for the app is that a stable stream at 720p beats a stuttering stream at 1080p every time.^[4]
• Kick's bitrate guide for the app puts 720p60 at 3,500 to 5,000 kbps and 1080p60 at 6,000 to 8,000 kbps, and advises keeping the bitrate under half your upload speed.^[4]
• The desktop equivalent is the same trade-off with different numbers. If you want ours worked out against your actual upload, the OBS bitrate calculator does it, and how to stream on Kick carries the full encoder profile.

# Four changes that make it worse

Each of these is a plausible response to seeing 720p, and each one costs you something while changing nothing about the cap.

1. Dropping your encoder to 720p to “match”. This is the expensive one. You now send a 720p source, so when the channel does become eligible there is no 1080p for Kick to serve, and your VODs are permanently 720p. Kick's instruction is the opposite: keep streaming in 1080p.^[1]
2. Pushing the bitrate to 8,000 to force a higher rung. Bitrate is an ingest setting and the ladder is a playback decision, so nothing is forced. What you do get is a heavier load on the same upload, which is how Kick's lag guide describes dropped frames arriving — your encoder producing video faster than the connection can send it.^[3]
3. Resetting the stream key. The key identifies your channel to the ingest server; it has no relationship to resolution eligibility. Kick's own warning about resetting is that your software then needs updating with the new key,^[2] which is a way to break a working stream in exchange for nothing.
4. Switching to VBR, H.265 or a rescale above 1080p. Kick answers all three directly: variable bitrate is not supported and CBR is required, only H.264 is supported, and Rescale Output should be enabled only if your base resolution exceeds 1920x1080.^[2] These changes get you a rejected or unstable stream, not a longer quality list.

# Telling the cap apart from a real fault

A platform cap and a genuine encoding problem can both end with someone saying the stream looks bad, so it is worth five minutes to know which one you have before changing anything. Run these in order and stop at the first one that answers.

1. Read the quality list, not the picture. If the top entry is 720p60 and the list below it runs 480p, 360p, 160p, Audio only, that is the documented capped ladder and you are done.^[1] A quality problem that is not the cap usually leaves 1080p present but ugly.
2. Check a large channel on the same device. 1080p there and not on yours confirms the limit is channel-side rather than player-side or network-side.
3. Look at dropped frames in your encoder. OBS shows the counter at the bottom right of the main window, and Kick's guide reads a climbing number as bitrate too high for the connection or an unstable network.^[3] A climbing counter is a real fault and has nothing to do with the cap.
4. Check CPU while live. Kick puts the line at 90 per cent and suggests a lighter preset — superfast on x264, P3: Fast on NVENC and AMD — or a switch to hardware encoding.^[3] Encoder overload produces smearing and stutter at any resolution.
5. Compare upload against bitrate. Kick's rule of thumb is upload at least twice your stream bitrate, so 6,000 kbps wants 12 Mbps available.^[3] Below that you have a real problem that the cap is masking rather than causing.

If steps three to five are all clean and the list still stops at 720p60, you have the cap and nothing else. The correct action at that point is to leave the settings where they are and keep streaming, which is an unsatisfying answer but the documented one.^[1] If the badge on your channel says something is wrong with the configuration, that is a separate signal with a separate cause — what the Misconfigured badge means covers it, and why a Kick stream keeps disconnecting covers drops.

# The bottom line

A Kick channel showing 720p60 at the top of its quality list is not misconfigured. It is a channel whose playback ladder does not include 1080p yet, sending a perfectly valid 1080p60 feed into an ingest that still accepts 1920x1080 at 60 fps and up to 8,000 kbps.^[2] Kick's instruction for that state is to change nothing and keep streaming in 1080p,^[1] which is the rare troubleshooting answer where doing less is correct.

What is worth knowing is the shape of the unknown. Kick publishes that the unlock is automatic and driven by growth and engagement, and publishes no threshold.^[1] The 75+ average CCV figure on that page belongs to the verification path, and Kick's Partner page puts verification before the 75 CCV requirement rather than after it.^[5] Anyone quoting you a precise viewer count for 1080p is quoting something Kick has not said. Keep the encoder at 1080p, fix the faults that are actually yours — dropped frames, CPU, upload headroom — and let the eligibility arrive on its own.