Legacy Upload Handling
Check whether an application accepts files with a .doc extension. Test how it responds when the extension and the actual content format do not match.
DOC generator
or choose a popular size below ↓
Download Sample DOC Files for Testing
Download a sample DOC file for testing legacy Word uploads, document conversion, and file handling. Choose a file size from 1 KB to 100 MB and use it in your testing workflow.
Download DOC
Format note: The current generated .doc file contains RTF content with a .doc extension. It can open in compatible word processors, but it is not a true binary Word 97–2003 document. Do not use it to verify binary DOC signatures or MIME detection.
Choose a Sample DOC File by Size
Select a file size that matches your testing needs.
| File Size | Suggested Use |
|---|---|
| 1 KB | Basic file acceptance |
| 10 KB | Small document uploads |
| 100 KB | Form and API testing |
| 500 KB | Medium file handling |
| 1 MB | Standard upload workflows |
| 5 MB | Conversion and preview testing |
| 10 MB | Processing and timeout checks |
| 25 MB | Larger file handling |
| 50 MB | Resource and worker testing |
| 100 MB | Large-file boundary testing |
For upload-limit tests, compare files below, at, and above your configured maximum. Confirm the actual file size before using it as a strict test fixture.
What Is Inside the Sample DOC File?
The current generated file contains Rich Text Format (RTF) content, which uses readable control syntax to represent formatted text. Its content begins with an RTF header, such as {\rtf1, rather than the binary structure expected from a genuine Word 97–2003 .doc file.
This distinction matters when testing applications that identify documents by their actual content rather than their filename.
The .doc extension alone does not prove that a file is a binary Word document. Because the current output contains RTF content, applications that inspect the file may identify it as RTF instead.
DOC File Technical Details
| Property | Current Output |
|---|---|
| File extension | .doc |
| Actual content format | RTF |
| RTF MIME type | application/rtf |
| RTF signature | {\rtf |
| True binary DOC MIME type | application/msword |
| True binary DOC signature | D0 CF 11 E0 A1 B1 1A E1 |
A genuine binary DOC file uses the OLE Compound File Binary Format. The current generated file should not be treated as a genuine binary DOC fixture.
For accurate format validation, compare the file's extension, detected content type, and internal structure. See the MIME types and file signatures reference.
What Can You Test With a Sample DOC File?
Document Conversion
Test the behavior of document conversion workflows using compatible software. Confirm that the converter handles the actual RTF content correctly rather than assuming the file is binary DOC.
File Validation
Check whether your validation logic relies only on a filename or also inspects the file content. The current output is useful for examining extension-based handling, but it is not suitable for confirming detection of a genuine binary DOC signature.
Preview and Error Handling
Test how your application responds when a document preview or processing service encounters the file. Record successful previews, rejected uploads, and clear error messages.
Download a Sample DOC File From the Command Line
You can request a generated file from the command line using curl.
This example requests the 1 MB file. Replace 1mb with another supported size as required. Verify the downloaded file's contents and byte size before using it in automated tests.
terminal
$ curl -L -o sample-1mb.doc "https://www.testfilelab.com/docs/generate/doc/1mb?download=1"Frequently Asked Questions
No. The current generated output contains RTF content with a .doc extension. It may open in compatible word processors, but it is not a true binary DOC file.
The file contains RTF content, identified by its RTF header. Content-based detection can therefore report an RTF MIME type even though the filename ends in .doc.
A genuine Word 97–2003 binary DOC file commonly uses application/msword. RTF content commonly uses application/rtf. Your application should inspect the actual file rather than relying on its extension alone.
Yes, you can use it to examine extension-based upload handling and file-size restrictions. However, do not use it as a fixture for tests that specifically require a genuine binary DOC file.
Get Started With Document Testing
Choose a file size and use the current sample DOC output to test upload behavior, conversion handling, and file validation. For tests that require a genuine binary Word document, use a verified binary DOC fixture instead.
Download DOC