> For the complete documentation index, see [llms.txt](https://docs.parallels.com/landing/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.parallels.com/landing/ras-admin-guide/v22-ja-jp/session-recording-experimental/session-recording-storage-structure/subtitle-files.md).

# サブタイトルファイル

各録画クリップには、録画されたセッションに関する情報が含まれた SRT 形式のサブタイトルファイルが付属しています。

例：

```
1
00:00:00,000 --> 00:00:02,000
Recorded: 2026-10-28 11:00:31
User: CONTOSO\jdoe
Machine: RDSH01
```

この字幕情報には、録画が作成された日時、録画されたユーザー、およびセッションをホストしているマシンが記載されています。

{% hint style="info" %}
**注：** 録画ファイルおよび関連するメタデータは、Parallels RAS によって自動的に管理されます。個々のファイルを手動で変更または削除すると、録画の整合性や再生に影響を与える可能性があるため、避けてください。録画の保存期間の管理には、設定された保存期間設定を使用してください。
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.parallels.com/landing/ras-admin-guide/v22-ja-jp/session-recording-experimental/session-recording-storage-structure/subtitle-files.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.