Inconsistent FileOptions Between JavaScript and C# Supabase Clients

Open
#184 2 comments 0 reactions 1 assignee View on GitHub

@Tr00d is already working on this.

Since Jul 3, 2026.

Assessment

This issue has not been assessed yet.

Description

parity

Description:
The FileOptions class in the C# Supabase client does not support all the options available in the JavaScript Supabase client. This discrepancy limits feature parity between the two implementations, making it difficult for developers to use the same configuration across different platforms.

Expected Behavior:
The FileOptions class in C# should support the same options as the JavaScript client, including:

duplex

headers

metadata

Reference:
For JavaScript implementation details, see Supabase JavaScript Storage Upload.

Actual Behavior:
Currently, the C# FileOptions class only includes:

cacheControl

contentType

upsert

Steps to Reproduce:

Try to use duplex, headers, or metadata in the C# client.

Observe that these options do not exist in the FileOptions class.

Suggested Fix:
Extend the FileOptions class in C# to include all options present in the JavaScript client for consistency and feature parity.

Environment:

Supabase C# SDK Version: 1.1.1

Dominant language
C#
Stars
701
Forks
106
Avg merge
16h 35m
Merged PRs (30d)
45

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from supabase/supabase-csharp

All issues in supabase/supabase-csharp

Similar issues

More C# issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.