<p>Per <a href="https://www.reddit.com/r/obs/comments/e3riv0/comment/f95cjvy/?utm_source=share&amp;utm_medium=web3x&amp;utm_name=web3xcss&amp;utm_term=1&amp;utm_content=share_button#:%7E:text=if%20you%20mouse%20over%20the%20filename%20box%2C%20a%20list%20of%20variables%20should%20pop%20up%20(does%20on%20windows%20v24.0.3)" rel="nofollow noreferrer">a helpful answer from reddit</a> (paraphrased):</p>
<blockquote>
<p>If you mouse over the filename box, a list of variables should pop up (does on Windows, version 24.0.3).</p>
</blockquote>
<p>...I've been able to acquire a list of valid variables, which I've formatted nicely (as an HTML table) at <a href="https://gitlab.com/-/snippets/4772474" rel="nofollow noreferrer"><code>gitlab.com/-/snippets/4772474</code></a>.</p>
<p>However, SE doesn't permit <code>th</code>s in a <code>tbody</code>, so I've provided them undermentioned as YAML:</p>
<pre class="lang-none prettyprint-override"><code>#!/usr/bin/env -S xdg-open
&quot;%CCYY&quot;: Year, four digits
&quot;%YY&quot;: Year, last two digits (00-99)
&quot;%MM&quot;: Month as a decimal number (01-12)
&quot;%DD&quot;: Day of the month, zero-padded (01-31)
&quot;%hh&quot;: Hour in 24h format (00-23)
&quot;%mm&quot;: Minute (00-59)
&quot;%ss&quot;: Second (00-59)
&quot;%%&quot;: A % sign
&quot;%a&quot;: Abbreviated weekday name
&quot;%A&quot;: Full weekday name
&quot;%b&quot;: Abbreviated month name
&quot;%B&quot;: Full month name
&quot;%d&quot;: Day of the month, zero-padded (01-31)
&quot;%H&quot;: Hour in 24h format (00-23)
&quot;%I&quot;: Hour in 12h format (01-12)
&quot;%M&quot;: Minute (00-59)
&quot;%p&quot;: AM or PM designation
&quot;%s&quot;: Time in seconds since UNIX epoch
&quot;%S&quot;: Second (00-59)
&quot;%Y&quot;: Year, last two digits (00-99)
&quot;%y&quot;: Year
&quot;%z&quot;: ISO 8601 offset from UTC in timezone
&quot;%Z&quot;: Timezone name or abbreviation
&quot;%FPS&quot;: Frames per second
&quot;%CRES&quot;: Base (canvas) resolution
&quot;%ORES&quot;: Output (scaled) resolution
&quot;%VF&quot;: Video format
</code></pre>
<p>Ultimately, <code>%z</code> provides what I desire.</p>

CC BY-SA 4.0
2024-11-23T13:12:36.140Z
2024-11-23T13:19:04.080Z
2024-11-23T13:19:04.080Z
RokeJulianLockhart
<p>I want the default filename to be ISO 8601-1:2019+A1:2022-compliant (because adhering to the ideal, RFC 9557, is infeasible). However, I've been unable to ascertain whether a variable exists for a numeric timezone. Usually, this is <code>%Z</code>, but this outputs <code>GMT</code> for me, instead of the desired <code>+0000</code> (expanded, <code>+00:00</code>) as would be specification-compliant. The best that I've achieved in this case is <code>+%CCYY%MM%DDT%hh%mm%ss%Z</code>.</p>
<p>For this use case and others, I want to more broadly know how to ascertain which values are permissible (and, ideally, what values they are able to output). I expect documentation to exist, but I've been unable to locate any.</p>

<obs><time>
What variables are permissible in OBS's "Filename Formatting" field?
RokeJulianLockhart
# What variables are permissible in OBS's "Filename Formatting" field?

(Asked by: username_0 on 2024-11-23)

I want the default filename to be ISO 8601-1:2019+A1:2022-compliant (because adhering to the ideal, RFC 9557, is infeasible). However, I've been unable to ascertain whether a variable exists for a numeric timezone. Usually, this is `%Z`, but this outputs `GMT` for me, instead of the desired `+0000` (expanded, `+00:00`) as would be specification-compliant. The best that I've achieved in this case is `+%CCYY%MM%DDT%hh%mm%ss%Z`.

For this use case and others, I want to more broadly know how to ascertain which values are permissible (and, ideally, what values they are able to output). I expect documentation to exist, but I've been unable to locate any.

**Tags:** obs, time


---

## 1 answers

### Answer by username_0 on 2024-11-23. Score: 0

Per a helpful answer from reddit (paraphrased):

If you mouse over the filename box, a list of variables should pop up (does on Windows, version 24.0.3).

...I've been able to acquire a list of valid variables, which I've formatted nicely (as an HTML table) at gitlab.com/-/snippets/4772474.
However, SE doesn't permit ths in a tbody, so I've provided them undermentioned as YAML:
#!/usr/bin/env -S xdg-open
"%CCYY": Year, four digits
"%YY": Year, last two digits (00-99)
"%MM": Month as a decimal number (01-12)
"%DD": Day of the month, zero-padded (01-31)
"%hh": Hour in 24h format (00-23)
"%mm": Minute (00-59)
"%ss": Second (00-59)
"%%": A % sign
"%a": Abbreviated weekday name
"%A": Full weekday name
"%b": Abbreviated month name
"%B": Full month name
"%d": Day of the month, zero-padded (01-31)
"%H": Hour in 24h format (00-23)
"%I": Hour in 12h format (01-12)
"%M": Minute (00-59)
"%p": AM or PM designation
"%s": Time in seconds since UNIX epoch
"%S": Second (00-59)
"%Y": Year, last two digits (00-99)
"%y": Year
"%z": ISO 8601 offset from UTC in timezone
"%Z": Timezone name or abbreviation
"%FPS": Frames per second
"%CRES": Base (canvas) resolution
"%ORES": Output (scaled) resolution
"%VF": Video format

Ultimately, %z provides what I desire.


---

