# Embedded vs Linked Libraries ### Embedded library An embedded library is a library that contains only **internal** functions. * If a smart contract is consuming a library which have only internal functions, then the EVM simply embeds the library into the contract (hardcoded into contract at compile time). * Instead of using `delegatecall` to call a function, it simply uses `JUMP` statement (normal method call). There is no need to separately deploy library in this scenario. ### Linked Library A linked library is a library that contains public or external functions. * The library needs to be deployed as a separate contract, and a unique address will be generated for it upon deployment. * This address needs to be linked with calling contract. --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://calnix.gitbook.io/aave-book/primer/embedded-vs-linked-libraries.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.