Skip to content

Quicken data file (.qsd)

.qsd file signature | application/octet-stream

Quicken data file

Safe

Magic Bytes

Offset 0
51 57 20 56 65 72 2E 20

Sources: Gary Kessler

Extension

.qsd

MIME Type

application/octet-stream

Byte Offset

0

Risk Level

Safe

Validation Code

How to validate .qsd files in Python

Python
def is_qsd(file_path: str) -> bool:
    """Check if file is a valid QSD by magic bytes."""
    signature = bytes([0x51, 0x57, 0x20, 0x56, 0x65, 0x72, 0x2E, 0x20])
    with open(file_path, "rb") as f:
        return f.read(8) == signature

How to validate .qsd files in Node.js

Node.js
function isQSD(buffer: Buffer): boolean {
  const signature = Buffer.from([0x51, 0x57, 0x20, 0x56, 0x65, 0x72, 0x2E, 0x20]);
  return buffer.subarray(0, 8).equals(signature);
}

How to validate .qsd files in Go

Go
func IsQSD(data []byte) bool {
    signature := []byte{0x51, 0x57, 0x20, 0x56, 0x65, 0x72, 0x2E, 0x20}
    if len(data) < 8 {
        return false
    }
    return bytes.Equal(data[:8], signature)
}

API Endpoint

GET /api/v1/qsd
curl https://filesignature.org/api/v1/qsd

See the full API documentation for all endpoints and parameters.

Frequently Asked Questions

What is a .qsd file?

A .qsd file is a Quicken data file file. Quicken data file

What are the magic bytes for .qsd files?

The magic bytes for Quicken data file files are 51 57 20 56 65 72 2E 20 at byte offset 0. These bytes uniquely identify the file format regardless of the file extension.

How do I validate a .qsd file?

To validate a .qsd file, read the first bytes of the file and compare them against the known magic bytes (51 57 20 56 65 72 2E 20) at offset 0. This is more reliable than checking the file extension alone, as extensions can be renamed.

What is the MIME type for .qsd files?

There is no officially registered MIME type for .qsd files. Systems typically use application/octet-stream as a generic fallback when handling this format.

Is it safe to open .qsd files?

Quicken data file (.qsd) files are generally safe to open. They are classified as low risk because they primarily contain data rather than executable code. However, always ensure files come from a trusted source.