Need help with UnderKeyboard?
Click the “chat” button below for chat support from the developer who created it, or find similar developers for support.

About the developer

130 Stars 20 Forks MIT License 150 Commits 3 Opened issues


An iOS libary for moving content from under the keyboard.

Services available


Need anything else?

Contributors list

# 53,644
22 commits
# 768,425
1 commit
# 18,268
1 commit

An iOS / Swift libary for moving content from under the keyboard

Carthage compatible CocoaPods Version License Platform

This library helps moving your views when a keyboard appears and move them back in place when it hides. It includes helper class for changing the length of a bottom Auto Layout constraint.

Moving content from under the keyboard in iOS / Swift


There are three ways you can add UnderKeyboard to your project.

Add source (iOS 7+)

Simply add UnderKeyboardDistrib.swift into your project.

Setup with Carthage (iOS 8+)

Alternatively, add

github "evgenyneu/UnderKeyboard" ~> 13.0
to your Cartfile and run
carthage update

Setup with CocoaPods (iOS 8+)

If you are using CocoaPods add this text to your Podfile and run

pod install
target 'Your target name'
pod 'UnderKeyboard', '~> 13.0'

Legacy Swift versions

Setup a previous version of the library if you use an older version of Swift.



import UnderKeyboard
to your source code if you used Carthage or CocoaPods setup methods.

Move content up

When a keyboard appears on screen it can obscure your views. One way of preventing it is to create a bottom Auto Layout constraint and increase its length. You can use the

helper class that does exactly that. Note that bottom layout constraint relation can be a simple
or it can be
greater than
relation that is used in the login screen of the demo app.
@IBOutlet weak var bottomLayoutConstraint: NSLayoutConstraint!
let underKeyboardLayoutConstraint = UnderKeyboardLayoutConstraint()

override func viewDidLoad() { super.viewDidLoad()

underKeyboardLayoutConstraint.setup(bottomLayoutConstraint, view: view) }

Increase height of bottom layout constraint when keyboard appears in iOS

Note: the bottom edge of the

should be connected to the superview and not to layout guide or safe area.

Using keyboard observer directly

This library includes the

class that you can use to write your own custom logic. You can supply functions that will be called by this observer when the keyboard is shown and hidden. Your function will receive the height of the keyboard. The hight argument is zero if the keyboard is being hidden.
let keyboardObserver = UnderKeyboardObserver()

override func viewDidLoad() { super.viewDidLoad() keyboardObserver.start()

// Called before the keyboard is animated keyboardObserver.willAnimateKeyboard = { height in myConstraint.constant = height }

// Called inside the UIView.animateWithDuration animations block keyboardObserver.animateKeyboard = { height in myView.layoutIfNeeded() } }

Getting height of the keyboard


property of the
object to get the current keyboard height. The
method must first be called to start listening for keyboard notifications. The value returned by
can be
if keyboard state is unknown. It can happen if no keyboard notifications occurred after the
method was called so we don't know if the keyboard is visible or hidden.
let keyboardObserver = UnderKeyboardObserver()

override func viewDidLoad() { super.viewDidLoad() keyboardObserver.start() }

func myFunction() { print("Keyboard height: (keyboardObserver.currentKeyboardHeight)") }

API change in version 11


attribute for
method of the
class was removed in version 11. In order to calculate the height of the bottom constaint correctly, its bottom edge should now be connected to the superview and not to layout guide or safe area. The superview should be the one that matches the size of the app window.


Managing Keyboard


UnderKeyboard is released under the MIT License.


Creature under the keyboard

We use cookies. If you continue to browse the site, you agree to the use of cookies. For more information on our use of cookies please see our Privacy Policy.