Get to know MDN better
This feature is well established and works across many devices and browser versions. It’s been available across browsers since July 2015.
Warning: The arguments passed to this constructor are dynamically parsed and executed as JavaScript. APIs like this are known as injection sinks, and are potentially a vector for cross-site-scripting (XSS) attacks.
You can mitigate this risk by always passing TrustedScript objects instead of strings and enforcing trusted types.
See Security considerations for more information.
The Function() constructor creates Function objects. Calling the constructor directly can create functions dynamically, but suffers from security and similar (but far less significant) performance issues as eval(). However, unlike eval (which may have access to the local scope), the Function constructor creates functions which execute in the global scope only.
Note: Function() can be called with or without new. Both create a new Function instance.
TrustedScript instances or strings specifying names to be used by the function as formal argument names. The value must correspond to a valid JavaScript parameter (any of plain identifier, rest parameter, or destructured parameter, optionally with a default), or a list of such strings separated with commas.
As the parameters are parsed in the same way as function expressions, whitespace and comments are accepted. For example: "x", "theValue = 42", "[a, b] /* numbers */" — or "x, theValue = 42, [a, b] /* numbers */". ("x, theValue = 42", "[a, b]" is also correct, though very confusing to read.)
functionBodyA TrustedScript or a string containing the JavaScript statements comprising the function definition.
Function parameter arguments can't be parsed as a valid parameter list, or the functionBody can't be parsed as valid JavaScript statements.
TypeErrorAny parameter is a string when Trusted Types are enforced by a CSP and no default policy is defined.
Function objects created with the Function constructor are parsed when the function is created. This is less efficient than creating a function with a function expression or function declaration and calling it within your code, because such functions are parsed with the rest of the code.
All arguments passed to the function, except the last, are treated as the names of the identifiers of the parameters in the function to be created, in the order in which they are passed. The function will be dynamically compiled as a function expression, with the source assembled in the following fashion:
This is observable by calling the function's toString() method.
However, unlike normal function expressions, the name anonymous is not added to the functionBody's scope, since functionBody only has access the global scope. If functionBody is not in strict mode (the body itself needs to have the "use strict" directive since it doesn't inherit the strictness from the context), you may use arguments.callee to refer to the function itself. Alternatively, you can define the recursive part as an inner function:
Note that the two dynamic parts of the assembled source — the parameters list args.join(",") and functionBody — will first be parsed separately to ensure they are each syntactically valid. This prevents injection-like attempts.
The method can be used to execute arbitrary input passed to any parameter. If the input is a potentially unsafe string provided by a user, this is a possible vector for Cross-site-scripting (XSS) attacks. For example, the following example assumes the untrustedCode was provided by a user:
Websites with a Content Security Policy (CSP) that specifies script-src or default-src will prevent such code running by default. If you must allow the scripts to run via Function(), you can mitigate these issues by always assigning TrustedScript objects instead of strings, and enforcing trusted types using the require-trusted-types-for CSP directive. This ensures that the input is passed through a transformation function.
To allow Function() to run, you additionally need to specify the trusted-types-eval keyword in your CSP script-src directive. The unsafe-eval keyword also allows Function(), but is much less safe then trusted-types-eval because it would allow execution even on browsers that do not support trusted types.
For example, the required CSP for your site might look like this:
The behavior of the transformation function depends on the specific use case that requires a user provided script. If possible, you should lock the allowed scripts to exactly the code that you trust to run. If that is not possible, you might allow or block the use of certain functions within the provided string.
Note that these examples omit the use of trusted types for brevity. For code showing the recommended approach, see Using TrustedScript in eval().
The following code creates a Function object that takes two arguments.
The arguments a and b are formal argument names that are used in the function body, return a + b.
| ECMAScript® 2027 Language Specification # sec-function-constructor |
Enable JavaScript to view this browser compatibility table.
This page was last modified on Jan 21, 2026 by MDN contributors.
Your blueprint for a better internet.
Visit Mozilla Corporation’s not-for-profit parent, the Mozilla Foundation.
Portions of this content are ©1998–2026 by individual mozilla.org contributors. Content available under a Creative Commons license.