This documentation is archived and is not being maintained.

Byte.Parse Method (String, NumberStyles, IFormatProvider)

Updated: July 2008

Converts the string representation of a number in a specified style and culture-specific format to its Byte equivalent.

Namespace:  System
Assembly:  mscorlib (in mscorlib.dll)

public static byte Parse(
	string s,
	NumberStyles style,
	IFormatProvider provider


Type: System.String

A string containing a number to convert. The string is interpreted using the style specified by style.

Type: System.Globalization.NumberStyles

A bitwise combination of NumberStyles values that indicates the style elements that can be present in s. A typical value to specify is NumberStyles.Integer.

Type: System.IFormatProvider

An IFormatProvider object that supplies culture-specific information about the format of s. If provider is null, the thread current culture is used.

Return Value

Type: System.Byte
The Byte value equivalent to the number contained in s.


s is null.


s is not of the correct format.


s represents a number less than Byte.MinValue or greater than Byte.MaxValue.


s includes non-zero, fractional digits.


style is not a NumberStyles value.


style is not a combination of NumberStyles.AllowHexSpecifier and NumberStyles.HexNumber values.

The style parameter defines the style elements (such as white space or the positive sign) that are allowed in the s parameter for the parse operation to succeed. It must be a combination of bit flags from the NumberStyles enumeration. Depending on the value of style, the s parameter may include the following elements:


Or, if the style parameter includes AllowHexSpecifier:


Elements in square brackets ([ and ]) are optional. The following table describes each element.




Optional white space. White space can appear at the beginning of s if style includes the NumberStyles.AllowLeadingWhite flag, or at the end of s if style includes the NumberStyles.AllowTrailingWhite flag.


A culture-specific currency symbol. Its position in the string is defined by the NumberFormatInfo.CurrencyPositivePattern property of the NumberFormatInfo object returned by the GetFormat method of the provider parameter. The currency symbol can appear in s if style includes the NumberStyles.AllowCurrencySymbol flag.


An optional positive sign. (The method throws an OverflowException if a negative sign is present in s.) The sign can appear at the beginning of s if style includes the NumberStyles.AllowLeadingSign flag, or at the end of s if style includes the NumberStyles.AllowTrailingSign flag.


A sequence of digits from 0 through 9.


A culture-specific decimal point symbol. The decimal point symbol of the culture specified by provider can appear in s if style includes the NumberStyles.AllowDecimalPoint flag.


One or more occurrences of the digit 0. Fractional digits can appear in s only if style includes the NumberStyles.AllowDecimalPoint flag.


The e or E character, which indicates that the value is represented in exponential notation. The s parameter can represent a number in exponential notation if style includes the NumberStyles.AllowExponent flag.


A sequence of hexadecimal digits from 0 through f, or 0 through F.

A string with decimal digits only (which corresponds to the NumberStyles.None style) always parses successfully. Most of the remaining NumberStyles members control elements that may be but are not required to be present in this input string. The following table indicates how individual NumberStyles members affect the elements that may be present in s.

Non-composite NumberStyles values

Elements permitted in s in addition to digits


Decimal digits only.


The . and fractional_digits elements. However, fractional_digits must consist of only one or more 0 digits or an OverflowException is thrown.


The s parameter can also use exponential notation.


The ws element at the beginning of s.


The ws element at the end of s.


A positive sign can appear before digits.


A positive sign can appear after digits.


Although this flag is supported, the use of parentheses in s results in an OverflowException.


Although the group separator symbol can appear in s, it can be preceded by only one or more 0 digits.


The $ element.

If the NumberStyles.AllowHexSpecifier flag is used, s must be a hexadecimal value. The only other flags that can be present in style are NumberStyles.AllowLeadingWhite and NumberStyles.AllowTrailingWhite. (The NumberStyles enumeration has a composite number style, NumberStyles.HexNumber, that includes both white space flags.)

The provider parameter is an IFormatProvider implementation, such as a NumberFormatInfo or CultureInfo object. The provider parameter supplies culture-specific information used in parsing. If provider is null, the thread current culture is used.

The following code example parses string representations of Byte values with this overload of the Byte.Parse(String, NumberStyles, IFormatProvider) method.

NumberStyles style;
CultureInfo culture;
string value;
byte number;

// Parse number with decimals. 
// NumberStyles.Float includes NumberStyles.AllowDecimalPoint.
style = NumberStyles.Float;     
culture = CultureInfo.CreateSpecificCulture("fr-FR");
value = "12,000";

number = Byte.Parse(value, style, culture);
Console.WriteLine("Converted '{0}' to {1}.", value, number);

culture = CultureInfo.CreateSpecificCulture("en-GB");
   number = Byte.Parse(value, style, culture);
   Console.WriteLine("Converted '{0}' to {1}.", value, number);
catch (FormatException) {
   Console.WriteLine("Unable to parse '{0}'.", value); }   

value = "12.000";
number = Byte.Parse(value, style, culture);
Console.WriteLine("Converted '{0}' to {1}.", value, number);
// The example displays the following output to the console: 
//       Converted '12,000' to 12. 
//       Unable to parse '12,000'. 
//       Converted '12.000' to 12.

Windows 7, Windows Vista, Windows XP SP2, Windows XP Media Center Edition, Windows XP Professional x64 Edition, Windows XP Starter Edition, Windows Server 2008 R2, Windows Server 2008, Windows Server 2003, Windows Server 2000 SP4, Windows Millennium Edition, Windows 98, Windows CE, Windows Mobile for Smartphone, Windows Mobile for Pocket PC, Xbox 360, Zune

The .NET Framework and .NET Compact Framework do not support all versions of every platform. For a list of the supported versions, see .NET Framework System Requirements.

.NET Framework

Supported in: 3.5, 3.0, 2.0, 1.1, 1.0

.NET Compact Framework

Supported in: 3.5, 2.0, 1.0

XNA Framework

Supported in: 3.0, 2.0, 1.0




July 2008

Added a condition for an OverflowException.

Information enhancement.